terraform-provider-redpanda

Use when scaffolding a brand-new resource or datasource in the terraform-provider-redpanda repo. Triggers on "add resource", "new datasource", "scaffold redpanda <thing>", or any work that creates a fresh redpanda/resources/<name>/ directory. Covers schema yaml, schemagen wiring, model generation, hand-written CRUD glue, provider registration, unit tests, acceptance tests, examples, and docs end-to-end. For modifying an existing resource use extend-redpanda-resource instead.

Use when adding or modifying fields/attributes on an EXISTING resource or datasource in terraform-provider-redpanda. Triggers on "add field X to redpanda_<name>", "extend the topic resource", "new attribute on redpanda_cluster datasource". For brand-new resources or datasources (no existing package), use add-redpanda-resource instead.

Use when diagnosing a bug in terraform-provider-redpanda — whether a user reports a runtime failure ("expected empty plan but resource has planned action(s)", "WARN ... removing from state", "Provider produced inconsistent result after apply") OR a proactive coverage audit finds a function whose purpose is uncovered at one or more test tiers. Walks the mock/fake parity investigation, layered-defense design, red-test-first sequencing, and tier-by-tier regression-guard placement. Covers the specific "mock-loop passes but live run fails" bug class that has been the dominant failure mode in this repo. For new feature work use add-redpanda-resource or extend-redpanda-resource instead.