l3montree-dev / l3montree-dev/devguard
Migrate Database to work with postgresql version 18
Open
Nobody has claimed this yet.
component/devguard-api
- Dominant language
- Go
- Stars
- 161
- Forks
- 43
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 37
Description
We are actually building postgresql version 17 container images already - but we are not using them in the dockerfile. Todo so, we need to make sure, that we wont kill our production database. Maybe we can add something like an initContainer to check if a migration needs to take place?
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 inspecting the Dockerfile and the existing PostgreSQL container image references, comparing how version 17 is built with how it is selected. Determine how a PostgreSQL 18 migration can be detected without risking the production database, and define completion as a safe migration path that uses the intended image.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, postgresql
- Domain
- databases, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100