interactive add-cloud does not reject invalid cloud names
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Won't Fix
|
High
|
Unassigned |
Bug Description
According to the SRS doc:
System must handle invalid cloud names
https:/
There is no specification of what cloud names are valid or invalid, but I believe that a name containing slash is invalid, because slash is used as a separator between cloud and region.
Names containing slash are not rejected, but they cannot be used, even though add-cloud gives example usage as though they can:
$ juju add-cloud
Cloud Types
maas
manual
openstack
vsphere
Select cloud type: manual
Enter a name for the cloud: foo/region
Enter the controller's hostname or IP address: asdf
Cloud "foo/region" successfully added
You may bootstrap with 'juju bootstrap foo/region'
$ juju bootstrap foo/region
ERROR unknown cloud "foo", please try "juju update-clouds"
I have also tried arbitrary unicode unicode characters such as "∃", and they are also accepted.
Changed in juju: | |
assignee: | Richard Harding (rharding) → nobody |
There's nothing wrong with allowing unicode, but you're right that if we use slash as a delimiter, we need to prevent people from making cloud names with that character, or give them a way to escape it... probably the former.