Add initial doc regarding Space migration #1587
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
jameskerr
approved these changes
May 5, 2021
docs/Migration-of-Spaces.md
Outdated
|
|
||
| When upgrading to GA Brim release `v0.25.0` or newer, any data you had stored | ||
| in Spaces that you wish to continue accessing will need to be migrated to | ||
| pools. The tooling to perform this migration is still under development. This |
There was a problem hiding this comment.
I see "Spaces" was capitalized but "pools" was lower case. Not sure which is correct but they seem on the same level.
There was a problem hiding this comment.
Good point @jameskerr. I just pushed a commit to capitalize the "Pool" references also. Merging!
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.
Part of the plan for #1567 includes an article we can link to from our Space migration UX. While we're hopeful the migration tools should be seamless enough that users shouldn't need to read any supplemental materials to use it, some things I hope to accomplish by having an article:
There's a bit of a chicken/egg snag where the article needs to exist before we can link to it from the tools, so here I've started a placeholder article with a stab at some minimal content. As the migration tooling comes together, I'll plan to expand it with screenshots and such.
While I took a crack at summarizing some of the goodness of Lakes/Pools, please don't mistaken this for official marketing copy. I fully expect we're going to to have many more words to say on these topics in the web site, blog posts, etc., and as that wording comes together I fully expect the summary can be revised accordingly. That said, if you think I badly misrepresented something or left out something essential, I'm all ears.