Repository creation (API/CLI/UI) should perform validation on name for Docker-based repositories
|Target version:||Sprint 40|
|Velocity based estimate||-|
|Release||Katello 2.1||Release relationship||Auto|
Since the name for a Docker-based repository need to match the exact 'upstream name' for an existing Docker image, we will need to perform some type of sanitation in the name field so that only the expected characters (i.e. a-z, 0-9, / and _) are allowed. If we don't perform any validation for Docker-based repos, then the user won't find out about this until he/she tries to synchronize it.
If no form validation can be performed (UI), then perhaps we should display some type of help text explaining what the rules are? Preferably all layers (API, CLI and UI) would fail to create the repository and provide some useful information so that the user can fix the name.
#3 Updated by Adam Ruzicka about 3 years ago
It would be good to include the definition of docker repository name format in the docs.
The format is:
[USERNAME/]REPOSITORY where USERNAME can contain lower case letters and digits, 4-30 characters (inclusive) REPOSITORY can contain lower case letters, digits, dashes, underscores and dots, 3-30 characters (inclusive)