Updated salesforce pg_restore docs #4382
Merged
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
axelstudios
force-pushed
the
task/update-salesforce-restore-docs
branch
from
d9a2703
to
9f024ef
Compare
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.
Any background context you want to provide?
Restoring a production database results in any scheduled tasks to inadvertently start running on the instance where the restore takes place
What's this PR do?
Updates the production database
pg_restoredocumentation with steps to disable Salesforce syncing once the restore is completedHow should this be manually tested?
After restoring a production database follow the updated steps in the documentation and ensure that the celerybeat periodic tasks related to Salesforce are disabled