Description
As part of the Open VSX migration to AWS, we need a safe and reproducible way to place open-vsx.org in read-only mode while keeping the service available.
The goal is to avoid disabling the service entirely during the migration, if possible. Instead, Open VSX should continue serving read-only traffic while blocking actions that write to the database, such as publishing new extensions and submitting reviews.
The target date for the migration is currently set to May 28. This needs to be ready and deployed to production before then.
Requirements
When read-only mode is enabled:
- Users can continue browsing and downloading extensions.
- Publishing is disabled.
- Authentication is disabled or restricted for regular users.
- Existing regular user sessions are logged out.
- Admin access remains possible, if needed for operations.
- A clear site banner explains that Open VSX is temporarily in read-only mode, with a link to the Eclipse Status page.
- Publish attempts return a clear error message.
- Other write operations that could be lost, such as reviews, are blocked.
- Developers should identify any operations where clarification is needed on whether they should be allowed or blocked.
- Download count handling is defined. For example, paused, ignored, or handled after migration.
- Rate limiting continues to work, if possible.
Outcome
Implement a reusable read-only mode for Open VSX to support the AWS migration and future maintenance events.
For enablement, the preferred option is to allow read-only mode to be enabled from the admin dashboard, so this does not require a new deployment. However, it is acceptable for a first phase to enable it through configuration and add the admin dashboard option after the upcoming migration.
I will leave it to the team to decide what is possible within the deadline. I am flexible on the technical approach and would appreciate recommendations if someone would like to suggest a different approach or solution.
//cc @JoeTot @manpreetkaur-arch @agafgfafa
Description
As part of the Open VSX migration to AWS, we need a safe and reproducible way to place open-vsx.org in read-only mode while keeping the service available.
The goal is to avoid disabling the service entirely during the migration, if possible. Instead, Open VSX should continue serving read-only traffic while blocking actions that write to the database, such as publishing new extensions and submitting reviews.
The target date for the migration is currently set to May 28. This needs to be ready and deployed to production before then.
Requirements
When read-only mode is enabled:
Outcome
Implement a reusable read-only mode for Open VSX to support the AWS migration and future maintenance events.
For enablement, the preferred option is to allow read-only mode to be enabled from the admin dashboard, so this does not require a new deployment. However, it is acceptable for a first phase to enable it through configuration and add the admin dashboard option after the upcoming migration.
I will leave it to the team to decide what is possible within the deadline. I am flexible on the technical approach and would appreciate recommendations if someone would like to suggest a different approach or solution.
//cc @JoeTot @manpreetkaur-arch @agafgfafa