Closed sttts closed 3 months ago
Double checked whether the configuration name flag --configuration-name=caas
helps. It doesn't.
It's a bug on its own that I don't get a message from the CLI before the server is even contacted that the configuration name is not passed. The doc says The name of the Configuration. This property is required for cloud control planes.
.
This definitely used to work. The fact that it's not working now is pointing to the need for more automated testing to catch these problems.
Closed as the introduction of spaces into cloud has fundamentally changed up
and this is no longer applicable.
What happened?
This might be a server error too. But creating a control plane from the command line seems to be broken.
How can we reproduce it?
Log into your account with
up
. Thenup ctp create some-name
.What environment did it happen in?
Prod.