GCP Region module

[bpmct]

A discussion dedicated to the GCP Region module. Share your thoughts, questions, and feedback here.

Module Scorecard

Presentation & Onboarding	Credential Hygiene	Restricted-Environment Readiness	Engineering Quality	Overall
17 / 17	16 / 20	N/A	5 / 10	81 / 100

Drilldown

Presentation & Onboarding — 17 / 17

Criterion	Max	Score	Notes
Configuration-mode examples	12	12	README documents four distinct examples covering the major modes: basic region selection (regions = ["us", "europe"]), GPU-only filtering (gpu_only = true), all-zones vs single-zone (single_zone_per_region = false), and custom default zone. Each example uses sensible defaults and shows the module.gcp_region.value output in context.
Visual preview	5	5	README embeds ; image verified to exist at 94.1 KB.

Credential Hygiene — 16 / 20

Criterion	Max	Score	Notes
Secrets marked sensitive	16	16	The module defines no sensitive inputs (no API keys, tokens, or credentials). All variables (regions, gpu_only, default, etc.) are non-sensitive configuration. README examples contain no inline secrets. Criterion is vacuously satisfied.
Non-hardcoded auth path	4	0	The module is a pure parameter helper and does not interact with GCP authentication. No auth path (ServiceAccount, IAM, API key helper, etc.) is documented in the README.

Restricted-Environment Readiness — N/A

The module downloads nothing, installs no tools, executes no scripts, and contacts no external endpoints. It is a static Terraform data "coder_parameter" block with a hardcoded zone map. All four sub-criteria are excluded by construction.

Engineering Quality — 5 / 10

Criterion	Max	Score	Notes
Input quality	6	3	All ten variables have clear description, sensible default, and explicit type. However, no validation blocks are present on any input. For example, regions could validate that entries match known GCP region prefixes, and default could validate it is a recognized zone. The absence of any validation on a module with ten inputs is a gap.
Test coverage	4	2	main.test.ts covers five scenarios (default output, custom default, GPU invalid/valid default, parameter ordering) via runTerraformApply. No .tftest.hcl file is present. The TypeScript tests cover the core business logic adequately, but the rubric expects .tftest.hcl to primarily cover business logic with TypeScript for e2e; the split is not met.

Overall — 81 / 100

Raw 38 / 47 → round(38 / 47 × 100) = 81

Track: Utility (parameter helper; no agent, IDE, or user-facing application)

---

Scored against SCORECARD.md on 2026-10-26 with solstice-1.