goauthentik / goauthentik/authentik

Maintenance / Read Only Mode

Open
#24,314 0 comments 0 reactions 0 assignees View on GitHub
enhancement enhancement/confirmed
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 1h
Merged PRs (30d)
644

Description

### Is your feature request related to a problem?

After updating, I recognised some major errors, but I couldn't roll back because of the changes to the database structures and the newly written data. It would be useful to be able to activate a read-only mode before updating, so that we can back up the database, update it, and then roll it back if necessary.

### Describe the solution you'd like

A maintenance mode that disables all write processes without failing.

### Describe alternatives that you've considered

The process involves shutting down completely, backing up the database, performing the update and rolling back if necessary. However, this approach incurs more downtime for simple logins.

### Additional context

_No response_

Contributor guide

Open the contributing guide

Research direction

The issue names no files, tests, or entry points, so the first step is to identify where write processes and login handling are implemented. Done means a maintenance mode can be enabled before an update, prevent writes without failing, and still allow simple logins while the database is backed up or rolled back.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.