-
Notifications
You must be signed in to change notification settings - Fork 244
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
Support Architectures in odo registry
#6959
Support Architectures in odo registry
#6959
Conversation
🔨 Deploy Preview deleted from internal cluster!
|
As the devfiles with no architecture delacred are compatible with all architectures, I think the result needs to include all the devfiles with no architecture. |
You mean when using |
Yes I agree that it would be confusing for other, non-arch, strings. The search would need to work on a "copy" of the devfiles indexes with the arch field set to the list of all arches when it is empty, but I'm not sure it is feasible |
Okay, that would be a good approach. Let me look into that. Thanks. |
Devfiles with no architecture declared are supposed to be compatible with all known architectures. Co-authored-by: Philippe Martin <[email protected]>
Changes done in |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
What type of PR is this:
/kind feature
/area registry
What does this PR do / why we need it:
This displays the Devfile stacks architectures in the
odo registry
output (both human-readable and JSON).It also makes the
--filter
flag search in the architectures.Which issue(s) this PR fixes:
Fixes #6804
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer:
Some examples:
odo registry
odo registry --details --devfile java-openliberty --devfile-registry Staging
Filtering by architecture
Note that Devfiles with no architectures are supposed to be compatible with all known architectures; that's why the output above returns Devfiles with no architectures.