Self-service on-premise postgres databases

[eliihen]

User story

As a developer on a team I want to be able to create a new on-premise postgres database in a user friendly manner so that we don’t have to use a ticketing system to order them to be created for us

Acceptance criteria

• There exists a way to create an on-prem database via the developer portal
• This workflow somehow uses the existing DB provisioning API that the DBAs (Lars Flatmo) have created
• Limitations of this wizard is communicated to the user, for example if there are any in terms of day two operations. Can the database be resized at a later date in the UI and so on
• We have decided if it is preferable to be able to both order a database through backstage and via a kubernetes custom resource. This can be reconsidered if very impractical

[martinhny]

Dbrator TODOS:

• authentication
• create database from crd
• create secrets in gsm
• Fix password saving flow, test that we can connect. Password should only be saved once
• Finish writing unit testing vmware client
• Write unit tests for vmware auth (token provider)
• Expand on chainsaw tests, improve mock_client responses
• Create tests for retry logic in chainsaw. What happens if API is down?
• Emit events
• Create prometheus metrics for failing databases
• Create prometheus metrics for orphaned databases
• Create git workflow for dependabot and tests
• Figure out permissions for dbrator service account (needs read and create on secrets)
• Deploy to sandbox