feat: module follow-ups, and L-07 reworded
- A Check met through a module is met by a value in the code: the modules Skill tells the author to set every input a Check depends on. - scripts/check-terraform-modules.py reports catalogued modules with a newer version, and watched modules that can now be used with the pinned provider. - L-07 no longer mentions a low-carbon location, which led to a Check about a region's carbon score that code cannot show. Reworded with the owner's approval. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -36,9 +36,9 @@ Published 2026-10-10, from lesson proposal 06.
|
||||
|
||||
## L-07: Verify location constraints
|
||||
|
||||
**Rule.** When a requirement specifies where resources must be provisioned, such as a designated region, multi-zone placement, or a low-carbon location, create a Check for the `region` or `location` argument on every applicable Element.
|
||||
**Rule.** When a requirement specifies where resources must be provisioned, such as a designated region or multi-zone placement, create a Check for the `region` or `location` argument on every applicable Element, naming the region the design uses. Do not write a Check about a property of the region that code cannot show, such as its carbon rating.
|
||||
|
||||
**Why.** Validation frequently catches missing location constraints. Without this Check, resources may be provisioned in default regions, violating compliance or sustainability requirements.
|
||||
**Why.** Validation frequently catches missing location constraints. Without this Check, resources may be provisioned in default regions, violating location requirements. A Check about a region's carbon rating cannot be verified from code and sends the design back.
|
||||
|
||||
Published 2026-10-10, from lesson proposal 07.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user