Skip to content

Commit efcfde5

Browse files
Add strict mode for the wrangler deploy command
1 parent a792ac0 commit efcfde5

File tree

1 file changed

+4
-0
lines changed

1 file changed

+4
-0
lines changed

src/content/docs/workers/wrangler/commands.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -320,6 +320,10 @@ None of the options for this command are required. Also, many can be set in your
320320
- `--containers-rollout` <Type text="immediate | gradual" /> <MetaInfo text="optional" />
321321
- Specify the [rollout strategy](/containers/faq#how-do-container-updates-and-rollouts-work) for [Containers](/containers) associated with the Worker. If set to `immediate`, 100% of container instances will be updated in one rollout step, overriding any configuration in `rollout_step_percentage`. Note that `rollout_active_grace_period`, if configured, still applies.
322322
- Defaults to `gradual`, where the default rollout is 10% then 100% of instances.
323+
- `--strict` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
324+
- Turns on strict mode for the deployment command, meaning that the command will be more defensive and prevent deployments which could introduce potential issues. In particular this mode makes sure that in non-interactive environments, if a deployment would potentially override remote settings then the deployment is prevented.
325+
- `--force` <Type text="boolean" /> <MetaInfo text="(default: false) optional" />
326+
- Disables strict mode (if set via `--strict`) so that potentially problematic deployments are no longer prevented.
323327

324328
<Render file="wrangler-commands/global-flags" product="workers" />
325329

0 commit comments

Comments
 (0)