Files
gcp_solution_architecture_a…/.scratch/lessons/issues/04-avoid-using-values-as-setting-names.md
Jonathan Boniface 71da0ed504
Some checks failed
validation / verify (push) Failing after 12s
chore: housekeeping from the runs of 2026-10-09
- An Execution's files are written as each Deliverable is submitted, marked
  in_progress, so a killed process or one waiting for its user leaves them on
  disk. A write removes files an earlier write left that it no longer has.
- A question about delivered work is answered from that Execution's solution
  guide by the reply writer; a question about the service is answered as
  before. Nothing is started for either.
- Lessons: prove writes only for lessons the Skill holds; the Skill records
  the vendored Skill versions the lessons were read against, status names any
  that changed, and a test fails until they are reviewed.
- Four more code patterns: Firestore, BigQuery, Eventarc and GKE.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-10 11:44:38 +01:00

30 lines
959 B
Markdown

# L-04: Avoid Using Values as Setting Names
Status: ready-for-agent
Deliverable: target_architecture
Evidence-key: 22ff1f5fed
Proposed: 2026-10-09
Published: 2026-10-09
## Rule
When writing a Check for a configuration block that takes a name and value, explicitly state the block's argument name instead of writing the expected value as if it were the setting itself.
## Why
Automated reviews may mistake specific expected values for invalid setting names, causing warnings and submission delays.
## Evidence
Seen in 2 of 21 Executions, 4 times in all: submit_deliverable refused: Not submitted. A review found: Check …: google_sql_database_instance has no setting named cloudsql.iam_authent.
## Proof
Not yet measured.
## Comments
Approved by the owner on 2026-10-09.
- 2026-10-09: retired. The schema review no longer reads a value written with dots (a database flag, a service name) as a setting, so the rule has nothing left to work around.