chore: require OCI references for dynamicArtifact in metadata validation#150
Draft
jonkoops wants to merge 1 commit into
Draft
chore: require OCI references for dynamicArtifact in metadata validation#150jonkoops wants to merge 1 commit into
dynamicArtifact in metadata validation#150jonkoops wants to merge 1 commit into
Conversation
The dynamicArtifact field is now required and must start with oci://ghcr.io. Metadata validation emits an error for missing or non-OCI values, and the update-overlay script fails hard if it encounters invalid state during PR creation. Refs: RHIDP-15484, RHDHPLAN-934, RHDHPLAN-256
|
jonkoops
changed the title
dynamicArtifact in metadata validation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The
dynamicArtifactfield in package metadata is now required and must be anoci://ghcr.ioreference. The validation script and update-overlay PR creation both fail explicitly when the field is missing or has an unexpected format.This should not be merged until RHDH 1.10 reaches EOL and all metadata in rhdh-plugin-export-overlays has been migrated to OCI references.
ETA late Feb or early March, once 2.2.0 is live. See dates at https://access.redhat.com/support/policy/updates/developerhub
Ref: https://redhat.atlassian.net/browse/RHIDP-15484