Goal:

• Propage the image name users enter during the image creation process to the images we register/upload to the hyperscalers (to the extent possible).

Acceptance Criteria:

• Image builder validates the image name, where the validation rules are an intersection of the constraints of each hyperscaler.
• To the extent possible, the given image name is propagated. Where image names are unique (azure? and definitely gcp), we do something smart.

Open questions:

• What exactly do we do in case of conflicts?
• Also for our S3 images?

Steps:

1. Enforce validation in image builder (db, api, ui)
2. Propagate per platform where possible (aws will be easiest)