TODO
Deprecate --store-compliance on extension validate. Use the config key instead:
validation:
store_compliance: true
Today three switches set the same field: the flag, SHOPWARE_CLI_STORE_COMPLIANCE=1, and the YAML key. It only gates validateAssets (source vs compiled asset pairing). The flag's "wipe validation.ignore" is broken anyway: the ignores are copied to toolCfg.ValidationIgnores before the wipe. So the flag just duplicates the YAML key.
Work
- Mark the flag deprecated and point to
validation.store_compliance
- Env var: keep it as an override and document it, or deprecate it along with the flag (drop the
os.Getenv branch in cmd/extension/extension_validate.go)
- Changelog and flag help text
- Remove the flag after the deprecation window; keep the config field and the gate
Keep the flag working until then so CI doesn't break.
Out of scope
TODO
Deprecate
--store-complianceonextension validate. Use the config key instead:Today three switches set the same field: the flag,
SHOPWARE_CLI_STORE_COMPLIANCE=1, and the YAML key. It only gatesvalidateAssets(source vs compiled asset pairing). The flag's "wipevalidation.ignore" is broken anyway: the ignores are copied totoolCfg.ValidationIgnoresbefore the wipe. So the flag just duplicates the YAML key.Work
validation.store_complianceos.Getenvbranch incmd/extension/extension_validate.go)Keep the flag working until then so CI doesn't break.
Out of scope
project validate