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
* feat(cli): add deploy --preserve-resources + destructive-delete guard (AI-426)
`checkly deploy --preserve-resources` detaches resources removed from code
(kept in the account, returned to UI management) instead of deleting them,
forwarding preserveResources to the deploy endpoint and rendering the removed
resources as "Detached" in the preview.
Default deploy now guards against silent data loss: for an interactive,
non-forced run a preflight dry-run surfaces any resources that would be
permanently deleted and requires an explicit confirmation (skipped by --force).
The pre-deploy summary also advertises --preserve-resources.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* feat(cli): read DETACHED deploy action from backend (AI-426)
The deploy preview now reads an explicit DETACHED action from the diff
instead of inferring detachment solely from the client-side
--preserve-resources flag. Detached resources render in their own
"Detached (kept in account, now UI-managed)" section, separate from
"Delete:".
Backwards compatible both ways: older backends that still return DELETE
for preserved resources are folded into the detached bucket when
--preserve-resources is set, and older CLIs simply ignore the unknown
DETACHED action (no crash, since the action field is an unvalidated
string matched by an if/else chain).
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* refactor(cli): address deploy --preserve-resources review feedback (AI-426)
- Add StatusPage and StatusPageService to PRETTY_RESOURCE_TYPES so they
render with friendly names in delete/detach previews and guards.
- Reword user-facing "UI" references to "Checkly Webapp".
- Replace the em dash before --preserve-resources with a period for
readability.
- Remove the transitional DELETE-to-detach display fallback in
formatPreview (and its now-unused preserveResources param); the backend
ships before the CLI and always emits DETACHED.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
* fix(cli): only send preserveResources deploy param when opted in (AI-426)
The /v1/projects/deploy endpoint rejects unknown query params, and the
deploy-side backend support for preserveResources is not deployed yet, so
sending preserveResources=false on every deploy made all deploys fail with
`"preserveResources" is not allowed` (all e2e deploy tests red).
preserveResources=false is identical to the backend's default (delete
resources removed from code), so omit the param unless the user opted in
with --preserve-resources. Default deploys are now byte-for-byte identical
to before the feature; the param only rides along when explicitly requested
(which requires the deploy-side backend support to ship first).
Also fix the merged projects-deploy unit test to drive the async
event-stream deploy, and update assertions to the conditional param.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
0 commit comments