Point the staging db service to the correct db#90
Merged
ohaiwalt merged 1 commit intoOperationCode:masterfrom Apr 28, 2019
Merged
Point the staging db service to the correct db#90ohaiwalt merged 1 commit intoOperationCode:masterfrom
ohaiwalt merged 1 commit intoOperationCode:masterfrom
Conversation
ohaiwalt
approved these changes
Apr 28, 2019
Member
ohaiwalt
left a comment
ohaiwalt
left a comment
There was a problem hiding this comment.
I can merge this, but fwiw this service is 100% not required. It was originally used to differentiate between staging/prod in the OpCode backend prior to using something like kustomize.io to describe those differences.
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
2 participants
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 fixes a copy-paste fail where the resources staging database is pointing at the DB for the OC backend instead of the resources db.