Use test database for dev - DO NOT MERGE #48
Closed
Conversation
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
The client has asked us to use their test database service in the dev environment (only). Please do not close the PR for this change as it may deploy to prod with the test database used instead of the prod database.
|
The Vanity URL for the dev deploy is https://smk-svt-api-gov-bc-ca.test.api.gov.bc.ca If this is a dev deploy, verify that it looks good, then merge the pull request to trigger prod deployment. If this is a prod deployment, view your prod deploy at the url above :) mentions / notifications: @michaelpnelson |
Contributor
Author
|
Changes in the test database have been moved to the production database. Removing this change. |
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.
The client has asked us to use their test database service in the dev environment (only). Please do not close the PR for this change as it may deploy to prod with the test database used instead of the prod database.