-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Possibility of updating "pullspecs" #181
Comments
As discussed offline, these changes would not be worth the incurred overhead. Looking into alternatives, for instance, using annotations to hold pull.specs for OSBS [1]. OSBS would retrieve the pull.specs from the annotations and replace all of the equivalent pull.specs listed in the CSV file with the SHA digests. The only issue is that the type of SHAs digests that are swapped in are manifest digest lists which are not supported by the OpenShift internal registry and will break our S2I feature. We need platform specific digests [1] https://osbs.readthedocs.io/en/latest/users.html#pullspec-locations |
@kyguy is this issue still relevant? |
Closing as this is no longer relevant, all issues have been fixed by internal services |
OSBS team is requesting we update env vars in our manifest files that specify multiple images/values to just specify one. This is to fall inline with their automation efforts with SHA digests. For example:
I know this format is used to support upgrades for AMQ Streams, so this issue is to discuss the feasibility/possibility of this being changed or if we should push back on the requirement. If it is possible, what should the format look like?
The text was updated successfully, but these errors were encountered: