Various documentation updates for data migration #6240
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
There were a couple of defective links that I resolved as well as making it more clear to readers that services should not be started back up until after loading data into the new environment. I also replaced the deploy step with a simple downtime end call because a deploy step is now included when starting the steps for rebuilding an environment.
Charl1996
approved these changes
Mar 7, 2024
minhaminha
approved these changes
Mar 7, 2024
|
I made another change to make it even more clear that Start new environment should not be run if migrating, so now it looks like: Does this seem like overkill? |
You can never be too careful with user facing docs! |
minhaminha
approved these changes
Mar 7, 2024
|
Sorry one more change. Made the text for "not" bold. |
minhaminha
approved these changes
Mar 8, 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.
I forgot I had #6216 open which has some overlapping changes. I'm going to move forward with this one first, and then resolve the conflicts on that PR separately.
There were a couple of defective links that I resolved as well as making it more clear to readers that services should not be started back up until after loading data into the new environment. I also replaced the deploy step with a simple downtime end call because a deploy step is now included when starting the steps for rebuilding an environment.
Environments Affected
None