docs: describe how to remove extensions from the private openvsx registry#3029
Merged
Conversation
|
Click here to review and test in web IDE: |
|
🎊 Navigate the preview: https://699ed922ade53800bc85506f--eclipse-che-docs-pr.netlify.app 🎊 |
b16611f to
e53bcf0
Compare
gtrivedi88
reviewed
Feb 24, 2026
| @@ -0,0 +1,199 @@ | |||
| You can remove extensions from your private OpenVSX registry in two ways: by using the OpenVSX Admin API (recommended) or by deleting the extension data directly in the PostgreSQL database. | |||
Contributor
There was a problem hiding this comment.
Suggested change
| You can remove extensions from your private OpenVSX registry in two ways: by using the OpenVSX Admin API (recommended) or by deleting the extension data directly in the PostgreSQL database. | |
| You can remove extensions from your private OpenVSX registry by using one of the following methods: | |
| * Use the OpenVSX administrator API (recommended). | |
| * Delete the extension data directly in the PostgreSQL database. |
gtrivedi88
reviewed
Feb 24, 2026
| You can remove extensions from your private OpenVSX registry in two ways: by using the OpenVSX Admin API (recommended) or by deleting the extension data directly in the PostgreSQL database. | ||
|
|
||
| [id="delete-extensions-admin-api"] | ||
| === Option 1: Delete extension using the OpenVSX Admin API |
Contributor
There was a problem hiding this comment.
Suggested change
| === Option 1: Delete extension using the OpenVSX Admin API | |
| == Deleting an extension by using the OpenVSX administrator API |
gtrivedi88
reviewed
Feb 24, 2026
| [id="delete-extensions-admin-api"] | ||
| === Option 1: Delete extension using the OpenVSX Admin API | ||
|
|
||
| This method uses an admin user and Personal Access Token (PAT) to call the Admin API. |
Contributor
There was a problem hiding this comment.
Suggested change
| This method uses an admin user and Personal Access Token (PAT) to call the Admin API. | |
| Use this method to call the administrator API with an administrator user and a personal access token (PAT). |
gtrivedi88
reviewed
Feb 24, 2026
|
|
||
| .Prerequisites | ||
|
|
||
| * Access to the OpenShift cluster where OpenVSX is deployed (namespace `openvsx`). |
Contributor
There was a problem hiding this comment.
Suggested change
| * Access to the OpenShift cluster where OpenVSX is deployed (namespace `openvsx`). | |
| * You must have access to the OpenShift cluster where OpenVSX is deployed (namespace `openvsx`). |
gtrivedi88
reviewed
Feb 24, 2026
|
|
||
| .Procedure | ||
|
|
||
| . Add the OpenVSX admin user and PAT to the database. |
Contributor
There was a problem hiding this comment.
Suggested change
| . Add the OpenVSX admin user and PAT to the database. | |
| . Add the OpenVSX administrator user and PAT to the database: |
gtrivedi88
reviewed
Feb 24, 2026
| + | ||
| [NOTE] | ||
| ==== | ||
| Use a strong, unique value instead of `openvsx_admin_token` for production. The PAT is passed in the API request URL. |
Contributor
There was a problem hiding this comment.
Suggested change
| Use a strong, unique value instead of `openvsx_admin_token` for production. The PAT is passed in the API request URL. | |
| Use a strong, unique value instead of `openvsx_admin_token` for production. The system passes the PAT in the API request URL. |
Contributor
|
@svor I have some updates regarding the flow and content. Here is what I'm thinking. |
gtrivedi88
reviewed
Feb 24, 2026
| * link:https://github.com/eclipse/openvsx/[Eclipse Open VSX sources] | ||
| * link:https://github.com/eclipse/openvsx/wiki/[Eclipse Open VSX documentation] | ||
|
|
||
| == Delete Extensions in a Private OpenVSX Registry |
Contributor
There was a problem hiding this comment.
Can we create a separate assembly for this? Generally Additional resources mark the end of the topic. if we want a new one, we can create assembly and then add that asembly to nav? This way we can have the same flow? WDYT?
…stry Signed-off-by: Valerii Svydenko <[email protected]>
f2719bd to
1548ef3
Compare
Signed-off-by: Valerii Svydenko <[email protected]>
Signed-off-by: Valerii Svydenko <[email protected]>
Signed-off-by: Valerii Svydenko <[email protected]>
Signed-off-by: Valerii Svydenko <[email protected]>
ibuziuk
approved these changes
Feb 25, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this pull request change?
Adds an additional section to the Running the Open VSX On-Premises documentation describing how to remove extensions from the Open VSX registry.
What issues does this pull request fix or reference?
https://issues.redhat.com/browse/CRW-10109
Specify the version of the product this pull request applies to
Dev Spaces 3.27.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.