Skip to content

Added description of "allow_no_delete" in migrations #2853

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 1 commit into
base: 4.6
Choose a base branch
from

Conversation

mnocon
Copy link
Contributor

@mnocon mnocon commented Jul 25, 2025

Copy link

Preview of modified files

Preview of modified Markdown:

Copy link

code_samples/ change report

Before (on target branch)After (in current PR)

code_samples/data_migration/examples/delete_content.yaml


code_samples/data_migration/examples/delete_content.yaml

docs/content_management/data_migration/importing_data.md@247:``` yaml
docs/content_management/data_migration/importing_data.md@248:[[= include_file('code_samples/data_migration/examples/delete_content.yaml') =]]
docs/content_management/data_migration/importing_data.md@249:```

001⫶-
002⫶ type: content
003⫶ mode: delete
004⫶ match:
005⫶ field: content_remote_id
006⫶ value: __REMOTE_ID__
007⫶ only_visible_content: true # Optional, default: true. If set to true, only visible content will be deleted.
008⫶ allow_no_delete: false # Optional, default: false. If set to true, the migration will not fail if no content is found using the specified criteria.

Download colorized diff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant