The OCM repository specs based on OCI repository specs are now featuring a normalization handler, which
can be used to map information provided as formal part of the OCI spec to OCM related parts.
THis is used to identify URL sub paths given by an OCIRegistry repo spec (which would not be allowed for OCI)
and transfer them into the subPath part of the OCM specification.
This now aligns the handling in the constructor functions with the deserialization of OCI related OCM repository specifications.
What type of PR is this? (check all applicable)
[x] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[x] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert
Related Tickets & Documents
Fixes open-component-model/ocm-project#126
Screenshots
Added tests?
[x] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help
[ ] Separate ticket for tests # (issue/pr)
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
[ ] 📜 README.md
[ ] 🙅 no documentation needed
Checklist:
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
Description
The OCM repository specs based on OCI repository specs are now featuring a normalization handler, which can be used to map information provided as formal part of the OCI spec to OCM related parts.
THis is used to identify URL sub paths given by an OCIRegistry repo spec (which would not be allowed for OCI) and transfer them into the subPath part of the OCM specification.
This now aligns the handling in the constructor functions with the deserialization of OCI related OCM repository specifications.
What type of PR is this? (check all applicable)
Related Tickets & Documents
Fixes open-component-model/ocm-project#126
Screenshots
Added tests?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?
Checklist: