Creating an NA <-> EU migration option #3005
Open
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've spent some time adding functionality to allow bi-directional space transfer(s) between NA and EU data centers as this functionality doesn't currently exist.
How it works:
contentful migrate datacenter --help ✔ at 18:35:19
migrate datacenter
Migrate a space between Contentful data centers
Options:
-h, --help Show help [boolean]
--source Source data center (na or eu)
[required] [choices: "na", "eu"]
--target Target data center (na or eu)
[required] [choices: "na", "eu"]
--source-space-id Source space ID [string] [required]
--target-space-id Target space ID [string] [required]
--environment-id Environment ID (e.g. master)
[string] [default: "master"]
--source-token Source CMA token [string] [required]
--target-token Target CMA token [string] [required]
--use-verbose-renderer Display progress in new lines instead of spinner
[boolean] [default: false]
--include-taxonomies Migrate taxonomies (Concepts & Concept Schemes)
before importing content [boolean] [default: false]
--source-org-id Organization ID where taxonomies should be exported
from [string]
--target-org-id Organization ID where taxonomies should be imported
to [string]
--skip-content-publishing Skips content publishing. Creates content but does
not publish it [boolean] [default: false]
An example:
contentful migrate datacenter
--source na
--target eu
--source-space-id
--target-space-id
--source-token
--target-token
--source-org-id
--target-org-id
--include-taxonomies
--skip-content-publishing
I have manually tested this and it works both ways, it allows you to include taxonomies if you use them as otherwise the space import will fail, if you don't use them then you can simple use --include-taxonomies false