Clarify partial data transfer stage filtering and preservation behavior - #3376
Closed
pwizla wants to merge 5 commits into
Closed
Clarify partial data transfer stage filtering and preservation behavior#3376pwizla wants to merge 5 commits into
pwizla wants to merge 5 commits into
Conversation
Add documentation explaining how --only and --exclude filters work with data transfer stages (content, files, config). Clarifies that omitted stages preserve destination data and documents the content-replace-keep-config workflow with a stage transfer matrix. Related to strapi/strapi#27322
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
|
The matrix contradicted the upstream engine matrix in strapi/strapi#27322 on --exclude files, omitted the --exclude media-library row, and claimed nothing is preserved by default. Media library records travel with content, so excluding files leaves records pointing at untransferred binaries. Also corrects the two quoted CLI prompts to match command.ts and scopes the --force caution to the stages actually transferred.
The warning claimed excluded types are deleted in the target instance, the opposite of the transfer page. Verified that import and transfer share the same parseRestoreFromOptions call, so the semantics are identical: omitted stages are preserved.
Adds the --throttle, --no-checksums and --verbose rows that were missing from the strapi transfer table, and harmonizes the --exclude-content-types wording across the export, import and transfer tables.
Four entries derived from the review of this PR, each verified against parseRestoreFromOptions, TransferGroupPresets and expandMediaLibraryPreset: the files preset covers binaries only while media library records ride the content stage, the default command always preserves admin and ignored types, omitted stages are preserved rather than deleted across import and transfer, and the quoted CLI confirmation prompts must be checked against command.ts.
Collaborator
Author
|
Superseded by #3385. |
This file contains hidden or 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
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.
This PR documents the partial data-transfer behavior clarified in strapi/strapi#27322: stages omitted via
--onlyor--excludepreserve destination data, while transferred stages are replaced.--exclude filesonly skips the assets stage, so media library records still transfer with content and can point at binaries that were never transferred, and that--exclude media-librarypreserves bothcommand.ts, and scopes the--forcecaution to the stages actually transferred--throttle,--no-checksumsand--verboserows to the transfer table in the CLI reference, and harmonizes the--exclude-content-typeswording across the export, import and transfer tablesDocuments #27322
Direct preview link 👉 here