Upgrade Metabase Postgres/Patroni
- Dominant language
- TypeScript
- Stars
- 10
- Forks
- 0
- Avg merge
- 20h 8m
- Merged PRs (30d)
- 30
Description
**Describe the task**
A clear and concise description of what the task is.
**Purpose**
The reason why this task is needed and/or what value it adds.
**Acceptance Criteria**
- [ ] first
- [ ] second
- [ ] third
** Additional context**
Reference table here: [version table](https://apps.nrs.gov.bc.ca/int/confluence/display/SUSTEAM/Application+Tool+Versions+Audit)
Add any other context about the task here.
Confirm this task meets our team [**Definition of Ready (DoR)**](https://www.figma.com/board/XmNkN600aAVWFCBmSDdt10/Team-Documents?node-id=1-2&t=Xjd6nHZZ7YlnoOrD-4) before moving to the **Next Sprint** column.
Confirm this task meets our team [**Definition of Done (DoD)**](https://www.figma.com/board/XmNkN600aAVWFCBmSDdt10/Team-Documents?node-id=3-21&t=Xjd6nHZZ7YlnoOrD-4) before moving to the **Done** column.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue provides no repository files, tests, or entry points, and its acceptance criteria are still placeholders. Start by reviewing the linked version table and clarifying the target versions and upgrade scope for Metabase, Postgres, and Patroni. Done should be defined by concrete, agreed acceptance criteria rather than the current template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- databases, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100