Description of problem:
The default container URLs (in environments/containers-default-parameters.yaml) point to the CDN and they won't be updated as the containers are updated and the tags change.
GUI users who use the CDN will need to update the tags one-by-one, which no user will agree to do.
GUI users who use satellite will also need to update the URLs one-by-one.
The only alternative option is to run the "prepare" commands to use the undercloud as a registry, but that needs to be done from the CLI and then patch the plan in swift with the outputted environment file.
Some automation needs to be provided in the GUI to bring all the URLs up to date without requiring the use of the CLI.
Reading the description if I understand it correctly - yes the prepare command needs to be possible to be triggered through GUI and user should be able to choose a tag which they want to use for the images to be downloaded. Also user should be able to review what containers are going to be deployed and exchange URL/path manually if they want to deploy modified (or custom) container.
They can change image location and registry through the GUI, it's just difficult to do a bulk transaction. That's the crux of this issue. Should we make the UI a blocker because we can't do bulk registry/container location changes?