Some checks failed
validation / verify (push) Failing after 10s
Evidence was grouped only by the kind of problem, and a group gets one lesson, so what kept recurring inside "validation proposed a Check" could not be seen. A proposed or unimplementable Check is now also counted under each provider setting or resource type it names; a subject seen in two or more Executions is its own group and reaches the curator past triage. Over 32 Executions that gave five proposals. The owner approved three, now published: L-07 location Checks, L-08 Cloud SQL backup encryption, L-09 backend service capabilities. L-10 is held for more evidence and L-11 rejected. Also: retiring a lesson marks its proposal, so publish no longer brings a retired lesson back. L-04 had returned to the Skill that way. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
472 B
472 B
Lessons: deployment guidance
Rules learned from earlier work. Follow every one that applies.
L-05: Include Required Arguments in Alert Policies
Rule. Always verify and include all required arguments (such as time window definitions) when configuring nested blocks in monitoring alert policies.
Why. Missing required arguments in nested blocks will cause Terraform validation to fail, preventing submission.
Published 2026-10-10, from lesson proposal 05.