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
docs: update terraform tutorial with default rollout policy (#910)
Update the rollout policy section to reflect the new default behavior
where Bytebase applies a default rollout policy with checkers when none
is found. Add explicit checker configuration examples with correct enum
values (ERROR_ONLY, STRICT) and comprehensive documentation of options.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude <[email protected]>
plan_check_enforcement = "STRICT" # Block on both errors and warnings
254
+
}
255
+
}
235
256
}
236
257
}
237
258
```
238
259
239
-
-`roles` is the list of roles that are allowed to click the button to deploy changes manually. Even if automatic rollout is enabled, manual approval is still needed while there is any automatic check failure.
260
+
**Key Configuration Options:**
261
+
262
+
-`automatic`: When `true`, changes deploy automatically after approval. When `false`, requires manual click to deploy.
263
+
-`roles`: List of roles allowed to manually deploy changes. Required even with automatic rollout, as manual approval is needed when checks fail.
264
+
-`checkers.required_issue_approval`: When `true`, requires issue approval before rollout.
265
+
-`checkers.required_status_checks.plan_check_enforcement`: Controls SQL plan check enforcement:
266
+
-`PLAN_CHECK_ENFORCEMENT_UNSPECIFIED`: Allow rollout regardless of plan check results (no enforcement)
267
+
-`ERROR_ONLY`: Block rollout only when plan check finds errors (default)
268
+
-`STRICT`: Block rollout when plan check finds errors or warnings (stricter for production)
0 commit comments