Update s3 bucket and file matching pattern for mongo replication #715
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
We no longer have mongo-normal direcorty in the govuk-integration-database-backups s3 bucket. Those are now in shared-documentdb. The file matching also stopped returning file name. It was not updated to match the end of the expression with `\>`
AgaDufrat
changed the title
|
Thanks for raising this PR @AgaDufrat! It looks like #732 has been raised since which has been merged and solved the issue. |
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 no longer have mongo-normal direcorty in the
govuk-integration-database-backups s3 bucket. Those are now in shared-documentdb.
The file matching also stopped returning file name. It was not updated to match the end of the expression with
\>