Switch AWS Postgres step to use Component Resource
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 7
- Forks
- 2
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 3
Description
We should switch the AWS Postgres Config step to mirror the Azure step and use the GrafanaPostgresResources Component Resources to define the Grafana pieces. Right now there's some duplicate logic between the AWS and Azure steps. This will require some Pulumi state surgery to preserve the existing Grafana roles/grants/dbs etc...while switching them to be managed by the component resource.
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 AWS Postgres Config step and comparing it with the Azure step that uses GrafanaPostgresResources Component Resources. Review the Pulumi state implications before changing resource ownership. Done means the AWS step uses the component resource without losing existing Grafana roles, grants, or databases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, go, postgres
- Domain
- cloud, databases, infrastructure
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100