Self-managed install fails when ESS legacy auth column is missing
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 218
- Forks
- 72
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 427
Description
Fresh self-managed installs can fail when the Cassandra schema does not include the legacy ESS authorization column still selected by supported ESS images.\n\nThe migration set should preserve legacy ESS authorization compatibility while the service transition to oauth_authorizations is in progress.\n\nScope:\n- Restore the legacy ESS authorization column for fresh schemas.\n- Seed the legacy service authorization entries needed by current ESS images.\n- Keep OAuth authorization data in place for the forward migration path.
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 locating the migration set that defines the Cassandra schema and the legacy ESS authorization entries. Verify fresh schemas restore the legacy column and seed the required entries while retaining OAuth authorization data for the forward migration path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cassandra, go
- Domain
- authentication, backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100