Soft Update ?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 44.8k
- Forks
- 4.9k
- Avg merge
- 21h 23m
- Merged PRs (30d)
- 607
Description
Problem Statement
We use Sentry in our production environment, and we go through the same ordeal with every update. Configuring Kafka for the update, running database migrations, and many other processes...
Solution Brainstorm
What if only API key information, projects, user information, etc., were protected, and there were a way to waive rights to the data? Let’s call this a “soft upgrade.” Could we implement an update where the system is brought up using a self-hosted Docker Compose setup—or by including a Helm chart—while the remaining data is purged from the system? Errors logs might occur again, but users and API keys must be protected.
Product Area
Releases
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the Releases area and the current update, migration, and self-hosted Docker Compose or Helm deployment paths. Define which user and API-key data must survive and which remaining data may be purged, then verify the proposed soft-update behavior against those requirements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, helm, python
- Domain
- devops, infrastructure, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100