Update devfile tests with OCI-based registry

[josephca]

What type of PR is this?
/kind cleanup

What does this PR do / why we need it:
After moving to use OCI-based registry (#4525), devfile tests should be using OCI-based registry as well.

Which issue(s) this PR fixes:

Related issues:
devfile/api#367
#4504
#4525

PR acceptance criteria:

• Unit test

• Integration test

• Documentation

• I have read the test guidelines

How to test changes / Special notes to the reviewer:
This PR is for changing test codes.

[josephca]

/assign @GeekArthur

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: josephca
To complete the pull request process, please assign prietyc123 after the PR has been reviewed.
You can assign the PR to them by writing /assign @prietyc123 in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• tests/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[rnapoles-rh]

@mohammedzee1000 Looks like both:

• https://registry.stage.devfile.io

and

• https://registry.devfile.io

have the same content, why use different URLs?

[josephca]

@mohammedzee1000 Looks like both:

• https://registry.stage.devfile.io

and

• https://registry.devfile.io

have the same content, why use different URLs?

@rnapoles-rh
I intentionally used two registries to test out different test cases against the official OCI-based registry vs. staging registry (contains the latest contents) and also to ensure the availability of both registries.

Here is the detail :

• Official registry (https://registry.devfile.io) updated weekly vs. staging registry(https://registry.stage.devfile.io) updated with PR merges.
• odo registry command test uses the official registry as it doesn't cause much overload on the public registry vs. odo catalog test uses the staging registry to avoid potential overload on the official registry.

[josephca]

@GeekArthur - please review. Thanks,

[girishramnani]

@mohammedzee1000 Looks like both:

• https://registry.stage.devfile.io

and

• https://registry.devfile.io

have the same content, why use different URLs?

@rnapoles-rh
I intentionally used two registries to test out different test cases against the official OCI-based registry vs. staging registry (contains the latest contents) and also to ensure the availability of both registries.

Here is the detail :

• Official registry (https://registry.devfile.io) updated weekly vs. staging registry(https://registry.stage.devfile.io) updated with PR merges.
• odo registry command test uses the official registry as it doesn't cause much overload on the public registry vs. odo catalog test uses the staging registry to avoid potential overload on the official registry.

So odo tests would fail if there is breaking changing in the staging registry? wouldn't that block us?

[prietyc123]

So odo tests would fail if there is breaking changing in the staging registry? wouldn't that block us?

Even I do feel the same. @josephca Currently the breaking changes in devfile registry are bothering us more and now it seems like we need to deal with staging one as well, no?

[josephca]

So odo tests would fail if there is breaking changing in the staging registry? wouldn't that block us?

Even I do feel the same. @josephca Currently the breaking changes in devfile registry are bothering us more and now it seems like we need to deal with staging one as well, no?

@girishramnani @prietyc123 Thanks for your inputs.
After discussion with devfile service team, it would be sufficient to test only with staging server. In addition, they will try to get some telemetry data in the future to track usage patterns on the community registry. Therefore, it will be good to use the staging server for testing to avoid polluting the data.

That said, I will update the code to use the staging server only.

[josephca]

/retest

[josephca]

/retest

[rnapoles-rh]

/lgtm

[josephca]

/assign @rnapoles-rh
Can you approve? Thanks,

[girishramnani]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: girishramnani, josephca

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• tests/OWNERS [girishramnani]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment