Procedures/managed openvsx registry - #3170
Conversation
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
|
🎊 Navigate the preview: https://6a689fa68e05fb299b0d3dff--eclipse-che-docs-pr.netlify.app 🎊 |
Add procedure for deleting extensions from the managed Open VSX registry using the admin API. Fix verification pod labels to use app.kubernetes.io/component instead of app=openvsx. Add NOTE about the registry starting empty. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
| {prod-short} supports three registry configurations: | ||
| {prod-short} supports four registry configurations: | ||
|
|
||
| Embedded Open VSX registry:: Runs in the `plugin-registry` pod and supports air-gapped, offline, and proxy-restricted environments. Contains a default subset of extensions that you can customize. |
There was a problem hiding this comment.
should we have an ordered list here 1 - 4 ?
|
|
||
| Embedded Open VSX registry:: Runs in the `plugin-registry` pod and supports air-gapped, offline, and proxy-restricted environments. Contains a default subset of extensions that you can customize. | ||
|
|
||
| Public Open VSX registry:: The community-hosted registry at `open-vsx.org`, accessed over the internet. Provides the full catalog of openly published extensions. |
There was a problem hiding this comment.
Also, we might want to highlight option 5: https://managed.open-vsx.org/pricing/
manged openvsx
| :page-aliases: | ||
|
|
||
| [id="enabling-the-managed-open-vsx-registry"] | ||
| = Enabling the managed Open VSX registry |
There was a problem hiding this comment.
let's clarify that this is tech-preview
There was a problem hiding this comment.
JTBD mapping
This content maps to Extend > Customize workspace tooling (extend_tooling), specifically Job 34: Control which editors developers can use. It belongs under assembly_deploying-private-registry (Deploy a private extension registry) alongside the existing self-hosted Open VSX procedures.
Merge sequencing recommendation
Option A (preferred): Merge PR #3143 (Extend JTBD restructuring) first, then rebase this PR to place the new file directly in the Extend module (modules/extend/). This avoids the file being added to administration-guide/ and then immediately moved.
Option B (acceptable): Merge this PR first if the feature needs docs before #3143 is ready. The person rebasing #3143 will need to:
- Move
enabling-the-managed-open-vsx-registry.adocfromadministration-guide/pages/toextend/pages/ - Add the
xref:toextend/nav.adoc(and remove it fromadministration-guide/nav.adoc) - Resolve 2-3 small merge conflicts in
managing-ide-extensions.adocandextensions-for-microsoft-visual-studio-code-open-source.adoc
This is roughly 15 minutes of rebase work, so not a blocker.
gtrivedi88
left a comment
There was a problem hiding this comment.
Re-posting misplaced inline comments at the correct lines. Apologies for the earlier confusion.
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
…sx-registry.adoc Co-authored-by: Gaurav Trivedi <90042568+gtrivedi88@users.noreply.github.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
Signed-off-by: Valerii Svydenko <vsvydenk@redhat.com>
| [role="_abstract"] | ||
| [IMPORTANT] | ||
| ==== | ||
| The managed Open VSX registry is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/. |
There was a problem hiding this comment.
| The managed Open VSX registry is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see https://access.redhat.com/support/offerings/techpreview/. | |
| The managed Open VSX registry is a Technology Preview feature only. |



What does this pull request change?
Provides documentation how to enable OpenVSX as a operand
What issues does this pull request fix or reference?
https://redhat.atlassian.net/browse/CRW-11147
Specify the version of the product this pull request applies to
7.121.0
Pull Request checklist
The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.
Validate language on files added or modifiedstep reports no vale warnings.