Menu
Executes code generation from Magic Modules into downstream Terraform providers and optionally compiles the binary.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
Skill for reviewing Magic Modules schemas. Currently covers the Enum vs. String decision via the knowledge base.
Opt resource into MMv1 list-resource generation by setting `generate_list_resource: true`, validate it locally, and open a one-resource PR against GoogleCloudPlatform/magic-modules. Invoke when the user asks to add list-resource support for a specific MMv1 resource or to enable `generate_list_resource` for an eligible resource.
Fallback workflow for general implementation and debugging tasks that do not involve creating a new resource.
Workflow specifically for creating a new resource, supporting both autogen and manual generation.
Create a Pull Request (PR) against GoogleCloudPlatform/magic-modules following repository standards, including branch management, commit formatting, mandatory release notes, pre-PR verification checks, and gh CLI commands.
Validate that changes to the generated providers don't introduce breaking changes or fields with missing tests or missing documentation. Use this skill when the user wants to check for breaking changes, missing tests, or missing documentation, or other problems in the downstream providers.
| name | generate-provider |
| description | Executes code generation from Magic Modules into downstream Terraform providers and optionally compiles the binary. |
generate-providerNote to AI Agents: You MUST read the YAML frontmatter above first. Only read the rest of this file if the
descriptionmatches your current roadblock or required task.
magic-modules root directory.$GOPATH environment variable must be set correctly.Set your variables and run the commands in sequence.
# 1. Define Variables
VERSION="beta" # or "ga"
PROVIDER_PATH="$GOPATH/src/github.com/hashicorp/terraform-provider-google-beta" # or "terraform-provider-google" for GA
MAGIC_MODULES_PATH="$(pwd)"
# Verify no uncommitted changes exist in the downstream provider directory.
# Stop if there are uncommitted changes and alert the user.
cd "$PROVIDER_PATH"
git status --porcelain
# 2. Code Generation (Run from Magic Modules root)
cd "$MAGIC_MODULES_PATH"
make provider VERSION=$VERSION OUTPUT_PATH="$PROVIDER_PATH"
# 3. Verify Changes (Run from Downstream Provider root)
cd "$PROVIDER_PATH"
# Verify that git status precisely matches the scope of your local Magic Modules edits.
# If you see "surprise" diffs in unrelated resources, ask the user if you should run `sync-provider` first.
git status --porcelain
# 4. Compile Binary (Already in Downstream Provider root)
make build