Repository navigation
docs(cli): a deploy owns a check's intent and automatic repair setting [RED-1193] - #580
Merged
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
…g [RED-1193] The write-back coverage list on the deploy page gains `intent` on the checks and monitors that take one. The intent snippet states the default (unset or null, the check has no intent), and the automatic-repair page says that for a check the CLI manages the intent and the repair setting belong in code: a deploy writes what the code declares, like every other property, and the plan lists an intent set in Checkly and can write it into the code. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…D-1193] Writing a value the way the construct spells it is what write-back does for every property, so the coverage list does not say so for intent. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
…193] The automatic-repair page and the Browser and Multistep Check construct references said omitting the property preserves the setting stored in Checkly. A deploy writes what the code declares, so an unset property means the same as null: the check follows the account default. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
sorccu
force-pushed
the
simo/red-1193-intent-owned
branch
from
October 16, 2026 11:05
681938b to
db984f5
Compare
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
RED-1193. The CLI now sends a check's
intentandaiAutoRepairEnabledwith every deploy, asnullwhen the code leaves them unset, so a deploy owns them like every other property and the plan can write an intent set in Checkly back into the code. The docs still described neither the default nor the write-back coverage, and three pages said omittingaiAutoRepairEnabledpreserves the setting stored in Checkly.What
cli/checkly-deploy.mdx:intentjoins the write-back coverage list, on the checks and monitors that take one.snippets/check-intent.mdx: the type isCheckIntent | nulland the default is stated (unset ornull, the check has no intent).resolve/automatic-check-repair.mdx: for a check the CLI manages, a deploy writes what the code declares, and the plan lists an intent set in Checkly and can write it into the code.resolve/automatic-check-repair.mdx,constructs/browser-check.mdx,constructs/multistep-check.mdx: an unsetaiAutoRepairEnabledfollows the account default, likenull; the sentence saying omission preserves an existing setting is gone.Merge with the CLI release that carries the change.
🤖 Generated with Claude Code