Missing validation/enforcement for environment name on create/update in CLI
Bug #1372498 reported by
Brian Tully
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-muranoclient |
Opinion
|
Undecided
|
Unassigned | ||
Bug Description
Through the Murano UI, when a user creates a new environment (or updates an existing environment) we run the "name" field through a validation function that warns the user if they have any "illegal" characters other than alphanumeric characters and underscores. However the CLI does not enforce this validation which can lead to some strangely named environments that are created in the CLI that do not validate in the UI. Ultimately, this leads to a confusing user experience.
Do environment names need to be validated/enforced in the UI, and if so, shouldn't they also be validated/enforced through the muranoclient CLI in order to be consistent?
| Changed in python-muranoclient: | |
| status: | New → Opinion |
Revision history for this message
| Andrew Pashkin (apashkin) wrote | #1 |
To post a comment you must log in.
They should be validated on server-side, I think.