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!
|








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 registryoutput (both human-readable and JSON).It also makes the
--filterflag 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.