feat: add support for asset scaning in import command - #157
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 |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
🔒 Security Scan Results
⏱️ SLA Breach Summary
ℹ️ Vulnerabilities Without Available Fixes (Informational Only)The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:
✅ BUILD PASSED - All security checks passed |
feat: add support for asset scaning in import command
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.