feat: introduce enhanced descriptor encoding and testing #543
Conversation
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
- Added support for new descriptor encoding types, including `jsonNormalisation/v4alpha1` and hashed variants (`sha256`, `sha512`), replacing ocm hash cv - Extended the `encodeDescriptors` function to handle new encoding types. - Integrated a comprehensive test for normalised and hashed descriptor encoding. - Updated CLI output flags and documentation to reflect new encoding options. Signed-off-by: Jakob Möller <jakob.moeller@sap.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does / why we need it
jsonNormalisation/v4alpha1and hashed variants (sha256,sha512), replacing ocm hash cvencodeDescriptorsfunction to handle new encoding types.Which issue(s) this PR fixes
This eventually completely supercedes
ocm hash cvwhich is needed to get us a signed component version (we need the hash that we output here later to sign our component version and verify its integrity)