getsentry / getsentry/self-hosted
Migration Hard Stops inforcement
Open
Bug
Waiting for: Product Owner
- Dominant language
- Shell
- Stars
- 9.6k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 15
Description
### Problem Statement
Hi
today I was upgrading a Sentry Self Hosted instance, But I was doing a wrong path,
I was expecting a meaning full error instead of a random error before running migration
### Solution Brainstorm
Like what we have in GitLab, It should check before running migration and raise a meaningful error and don't start at all
### Product Area
Unknown
Contributor guide
Research direction
The issue names no files or tests. Start by tracing the self-hosted upgrade path and where migrations are invoked, then compare the desired preflight behavior with GitLab's migration checks. Done means an invalid upgrade path is detected before migration starts and produces a meaningful error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker-compose, shell
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100