It seems it is currently possible to add clouds with invalid names.

We had a restricted cloud configured with the name `mydomain.com environment` that saved properly and didn't report any issues on testing the connection.

However when trying to enable the restricted cloud on a folder it would save the change without complaints but it checking the config again it would still not be selected. No logs are written anywhere and after a lot of debugging I traced it to the cloud name. changing it to `mydomain-com-environment` worked in the end.