You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add `--activate` flag to `code deploy` for activating a code version after deploy without the toggle behavior of `--reload`. Both `--activate` and `--reload` now error on failure instead of silently continuing.
The **setup** step installs the CLI and configures credentials for all subsequent steps. Everything after that — your build, version calculation, and deploy — can focus on your project's needs.
@@ -169,7 +169,7 @@ Deploy cartridges with typed inputs.
169
169
| Input | Default | Description |
170
170
|-------|---------|-------------|
171
171
|`cartridge-path`|`.`| Path to cartridge source directory |
172
-
|`reload`|`true`| Activate code version after deploy |
172
+
|`activate`|`false`| Activate code version after deploy |
173
173
|`code-version`| — | Code version (overrides env) |
174
174
|`cartridges`| — | Comma-separated cartridges to include |
175
175
|`exclude-cartridges`| — | Comma-separated cartridges to exclude |
'Failed to activate code version "{{version}}": {{message}}\n\nEnsure your OCAPI client ({{clientId}}) is configured with Data API permissions.\nSee: https://salesforcecommercecloud.github.io/b2c-developer-tooling/guide/authentication.html#ocapi-configuration',
0 commit comments