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
Copy file name to clipboardExpand all lines: README.md
+198-3Lines changed: 198 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -183,6 +183,203 @@ Both build and deployment events support these statuses:
183
183
184
184
Aliases like `success`, `in_progress`, `cancelled`, etc. are automatically normalized.
185
185
186
+
## Preflight Checks
187
+
188
+
When tracking a deployment with `--status=started`, the API automatically runs **preflight checks** to validate the deployment before it proceeds. These checks help enforce deployment policies and prevent common issues.
189
+
190
+
### What Gets Checked
191
+
192
+
Preflight checks validate:
193
+
194
+
1.**Concurrent Deployments** - Prevents multiple simultaneous deployments to the same environment
195
+
2.**No-Deploy Windows** - Blocks deployments during scheduled blackout periods (e.g., Friday afternoons)
196
+
3.**Flow Requirements** - Ensures versions are deployed to prerequisite environments first (e.g., staging before production)
197
+
4.**Soak Time** - Requires versions to run in an environment for a minimum duration before promoting
198
+
5.**Quality Approvals** - Requires QA/security sign-off from prerequisite environments
199
+
6.**Release Approvals** - Requires manager/lead approval before deploying to sensitive environments
200
+
201
+
### Exit Codes
202
+
203
+
The CLI uses specific exit codes to indicate different failure types:
204
+
205
+
-**0** - Success (deployment allowed)
206
+
-**1** - General error (network issues, invalid arguments)
0 commit comments