feat: add support for asset scaning in import command#157
Open
naman-contentstack wants to merge 2 commits into
Open
feat: add support for asset scaning in import command#157naman-contentstack wants to merge 2 commits into
naman-contentstack wants to merge 2 commits into
Conversation
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
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.
Summary
Adds automatic detection of the Asset Scanning feature on the org's plan during the import flow. When the org has either assetsScan (CMS assets) or amAssetsScan (DAM/CS Assets) enabled in its plan, the import command now skips the asset publish step automatically — no manual flag required.
Adds assetScanningEnabled to ImportConfig to carry the detected state through the import pipeline.
When publish is skipped due to scanning, a clear guidance message is logged after import completes, directing the user to run csdx cm:stacks:bulk-assets --data-dir ./content once scanning finishes.