Plugins » Katello

As a user, I can expect container repo names to follow the latest standard
Cloned from 16208653

Currently, container image names in Katello use dashes as delimiters between org, product, content view, etc. We should likely switch to slashes `/` because that seems to be the standard these days with container namespacing rules.. This should also help users read the names more easily.

Switching the convention is easy. What is not easy is migrating users. Considerations: # Migrating all container repositories to the new naming convention is likely a bad idea because users will have no time to get used to the change. # Users who have custom container naming schemes will expect to have those schemes respected.

Container repositories have all their names updated when their lifecycle environment receives a change to the container naming pattern via API. ::Actions::Katello::PublishContainerRepositories is responsible for this.

Idea: * For lifecycle environments that don't have a custom lifecycle environment container naming scheme, any new repositories should use the new naming scheme.  Old repositories should continue to use the old naming. ** `set_container_repository_name` gets run as part of active record validations, so we'll need to ensure that the container repository name stays the same for existing repositories. *** The repository name by default uses object labels, so we can assume that the user won't trigger an update that would cause a necessary change to the container repository name. * For lifecycle environments that do use a custom LCE container naming scheme, if the user removes that scheme, switch the container repositories to the new naming scheme.