[ASCN-382] Split secrets for Exceptional and Status #18
Conversation
This file contains 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
WouterDeKort
changed the title
stephen-vakil
previously approved these changes
Nov 14, 2024
aalear
reviewed
Nov 14, 2024
aalear
approved these changes
Nov 14, 2024
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.
This PR is for ASCN-382.
DBRE uses two sets of credentials for OpServer:
This PR adds a second set of secrets and splits the Sql secrets we use for Exceptional and Sql Status so we can configure this correctly in prod. For
ascn-dev, I added the required secrets and deployed successfully from local CNAB.I also asked Aaron if each app should have its own Exceptional credentials here since I think we now share the
db-Exceptions-Userbetween all apps and I don't think that's correct.