Files
gcp_solution_architecture_a…/.scratch/lessons/issues/08-cloud-sql-backup-encryption.md
Jonathan Boniface 5feaaa6271
Some checks failed
validation / verify (push) Failing after 10s
feat: lessons from what recurs about one setting, and three more approved
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>
2026-10-10 12:47:18 +01:00

807 B

L-08: Cloud SQL backup encryption

Status: ready-for-agent Deliverable: target_architecture Evidence-key: 08d64df049 Proposed: 2026-10-10 Published: 2026-10-10

Rule

When writing a Check for CMEK encryption on a google_sql_database_instance, do not require an encryption_key_name argument for backup storage, as the instance-level encryption_key_name automatically encrypts backups as well.

Why

The database instance resource does not have a separate encryption key argument for backups. Asking for one causes validation to reject the Check as un-implementable.

Evidence

Seen in 3 of 32 Executions, 3 times in all: a Check about google_sql_database_instance asked for something that resource cannot do.

Proof

Not yet measured.

Comments

Approved by the owner on 2026-10-10.