(CM-146) Update database name#15
Merged
Merged
Conversation
We’ve removed the `GovUk` prefix, so let’s remove it here too.
cf9a88b to
928e398
Compare
edavey
approved these changes
Sep 2, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We'd setup the prod database name to be
content_block_manager_production(as defined in the secret here https://github.com/alphagov/govuk-helm-charts/blob/517899d7fe694bf61b611d43e29b69d1c68b9c09/charts/external-secrets/templates/content-block-manager/postgresql.yaml#L20), which is different to what's in the database.yml, so the pods aren't coming up cleanly.The database names we do have use the
govukprefix, which we removed from the repo name. Rather than keep the old legacy name, let's change it to something predictable. I've also removed theGovukprefix from the app name to keep things consistent.