boris/keywarden
1
1
Fork 0
Code Issues 4 Pull Requests Actions Packages Projects 1 Releases Wiki Activity

Configure database migrations with Alembic #2

New Issue
Open
opened 2025-09-23 14:16:33 +00:00 by boris · 0 comments
boris commented 2025-09-23 14:16:33 +00:00
Owner
Copy Link

As a developer, I need Alembic migrations so that the database schema is versioned and reproducible across environments

Acceptance Criteria (G/W/T)

  • Given a fresh Postgres instance, when I run alembic upgrade head, then the base tables are created: users, servers, ssh_keys, access_requests, audit_events.
  • Given CI, when the workflow runs, then Alembic applies migrations successfully using KEYWARDEN_POSTGRES_* env vars (with sensible defaults).
  • Given a code change to models, when I run alembic revision --autogenerate, then a migration file is produced showing only intended diffs.

Notes / Non-functional

  • Alembic does not import full app settings (no SECRET_KEY required).
  • Naming convention applied (stable constraint/index names).
As a developer, I need Alembic migrations so that the database schema is versioned and reproducible across environments Acceptance Criteria (G/W/T) - [x] Given a fresh Postgres instance, when I run alembic upgrade head, then the base tables are created: users, servers, ssh_keys, access_requests, audit_events. - [x] Given CI, when the workflow runs, then Alembic applies migrations successfully using KEYWARDEN_POSTGRES_* env vars (with sensible defaults). - [ ] Given a code change to models, when I run alembic revision --autogenerate, then a migration file is produced showing only intended diffs. Notes / Non-functional - [x] Alembic does not import full app settings (no SECRET_KEY required). - [x] Naming convention applied (stable constraint/index names).
boris added this to the Minimum Viable Product milestone 2025-09-23 14:16:33 +00:00
boris added the
Kind/Feature
Priority
High
2
 labels 2025-09-23 14:16:33 +00:00
boris self-assigned this 2025-09-23 14:16:33 +00:00
boris added this to the Keywarden project 2025-09-23 14:16:33 +00:00
boris moved this to Review in Keywarden on 2025-09-23 14:16:35 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
1
The priority is critical
Priority
High
2
The priority is high
Priority
Low
4
The priority is low
Priority
Medium
3
The priority is medium
Reviewed
Confirmed
1
Issue has been confirmed
Reviewed
Duplicate
2
This issue or pull request already exists
Reviewed
Invalid
3
Invalid issue
Reviewed
Won't Fix
3
This issue won't be fixed
Status
Abandoned
3
Somebody has started to work on this but abandoned work
Status
Blocked
1
Something is blocking this issue or pull request
Status
Need More Info
2
Feedback is required to reproduce issue or to continue work
No Label
Kind/Feature
Priority
High
2
Milestone
No items
No Milestone Minimum Viable Product
Projects
Clear projects
No project Keywarden
Assignees
Clear assignees
boris
No Assignees boris
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: boris/keywarden#2
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?