feat: Configure Open VSX registry URL

[tolusha]

Signed-off-by: Anatolii Bazko abazko@redhat.com

What does this PR do?

feat: Configure Open VSX registry URL

Screenshot/screencast of this PR

N/A

What issues does this PR fix or reference?

eclipse-che/che#21598

How to test this PR?

N/A

PR Checklist

As the author of this Pull Request I made sure that:

• The Eclipse Contributor Agreement is valid
• Code produced is complete
• Code builds without errors
• Tests are covering the bugfix
• Custom resource definition file is up to date
• OLM bundles are up to date
• The repository devfile is up to date and works
• Sections What issues does this PR fix or reference and How to test this PR completed
• Relevant user documentation updated
• Relevant contributing documentation updated
• CI/CD changes implemented, documented and communicated

Reviewers

Reviewers, please comment how you tested the PR when approving it.

[l0rd]

Suggested change

	// Open VSX registry URL.
	// Open VSX registry URL. If omitted an embedded instance will be used.
	// To use the Eclipse Foundation operated online service set to `https://openvsx.org`

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: l0rd, tolusha

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

Needs approval from an approver in each of these files:

• OWNERS

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

[benoitf]

I'm wondering if we need 'Registry' in the name of the field OpenVSXRegistryURL or just OpenVSXURL ?
but no strong opinion on both choices

[l0rd]

I'm wondering if we need 'Registry' in the name of the field OpenVSXRegistryURL or just OpenVSXURL ? but no strong opinion on both choices

Yeah maybe that may be better since we already have the registry word in the pluginRegistry.

[openshift-ci]

New changes are detected. LGTM label has been removed.

[tolusha]

@benoitf
devworkspace-happy-path is very unstable. I always tries to investigate logs to find out the number of failed tests.
It is usually like:

  19 passing (10m)
  1 failing

So, I count it as good to merge if all other PR checks passed.

[openshift-ci]

@tolusha: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/v9-devworkspace-happy-path	2b46861	link	true	/test v9-devworkspace-happy-path
ci/prow/v11-devworkspace-happy-path	2b46861	link	true	/test v11-devworkspace-happy-path

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.