Skip to main content

dev-overrides

Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.

소스 정보

저장소
GoogleCloudPlatform/magic-modules
최근 소스 활동
2026년 5월 14일 21:22
감지된 SKILL.md 언어
영어
스타
975
포크
2,573

설치 방법

기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.

소스 파일 검토

설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.

SKILL.md 표시 중

SKILL.md
소스 지침 · 읽기 전용 미리보기
name
dev-overrides
description
Configures Terraform CLI with developer overrides to test locally built provider binaries without full Go acceptance tests, enabling rapid plan/apply cycles.
# `dev-overrides` > **Note to AI Agents:** You MUST read the YAML frontmatter above first. Only read the rest of this file if the `description` matches your current roadblock or required task. ## Prerequisites * You must have successfully compiled a local provider binary using the `generate-provider` skill. * You need a directory containing the `.tf` configuration you want to test. ## Execution Steps ### 1. Verification Ensure the provider binaries exist in the expected output paths. #### Verify Built Binaries ```bash # Verify the binaries were built (modify paths as necessary based on your host OS) ls -lh $GOPATH/bin/terraform-provider-google* ``` ### 2. The Core Commands Create a `.terraformrc` file referencing the local binaries and invoke Terraform with it. #### Setup Overrides and Test ```bash # 1. Create the dev override file dynamically cat << EOF > /tmp/tf-dev-override.tfrc provider_installation { dev_overrides { "hashicorp/google" = "${GOPATH}/bin" "hashicorp/google-beta" = "${GOPATH}/bin" } direct {} } EOF # 2. Navigate to your test directory and run terraform using the override # cd /path/to/test-directory TF_CLI_CONFIG_FILE="/tmp/tf-dev-override.tfrc" terraform plan # TF_CLI_CONFIG_FILE="/tmp/tf-dev-override.tfrc" terraform apply -auto-approve ``` ### 3. Verification & Handoff * Verify Terraform warns that "Provider development overrides are in effect." * Once the behavior is validated via plan/apply outputs, proceed to write the formal Go acceptance tests.
GitHub에서 보기