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 be in the relevant provider root directory, e.g., $GOPATH/src/github.com/hashicorp/terraform-provider-google-beta.
You must know the specific service path (e.g., ./google-beta/services/compute) and test name (e.g., TestAccComputeInstance_basic) you wish to run.

Execution Steps

1. Verification

Verify Directory Structure

pwd # Verify we are in the generated provider directory

2. The Core Commands

Run the acceptance test with TF_LOG=DEBUG enabled, and stream the output to a log file (test_output.log) so it can be parsed later if it fails.

Execute Acceptance Test

# Replace <SERVICE_NAME> and <TEST_NAME> with the appropriate values
TF_LOG=DEBUG make testacc TEST=./google-beta/services/<SERVICE_NAME> TESTARGS='-run=<TEST_NAME>$$' > test_output.log 2>&1

3. Verification & Handoff

If the test succeeds, return to your primary workflow.
If the test fails, do NOT attempt a blind fix immediately. You MUST invoke the parse-debug-logs skill on test_output.log to understand the API failure before proposing a fix.

Más de este repositorio

mismo repositorio

schema-review

GoogleCloudPlatform/magic-modules

Skill for reviewing Magic Modules schemas. Currently covers the Enum vs. String decision via the knowledge base.

2026-07-20964

add-list-resource-workflow

GoogleCloudPlatform/magic-modules

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.

2026-07-20964

default-workflow

GoogleCloudPlatform/magic-modules

Fallback workflow for general implementation and debugging tasks that do not involve creating a new resource.

2026-07-20964

new-resource-workflow

GoogleCloudPlatform/magic-modules

Workflow specifically for creating a new resource, supporting both autogen and manual generation.

2026-07-20964

create-pr

GoogleCloudPlatform/magic-modules

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.

2026-07-16964

validate-provider-changes

GoogleCloudPlatform/magic-modules

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.

2026-07-14964

name	run-acctests
description	Executes acceptance tests (testacc) for a specific resource or suite in the provider and outputs verbose debug logs.

`run-acctests`

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 be in the relevant provider root directory, e.g., $GOPATH/src/github.com/hashicorp/terraform-provider-google-beta.
You must know the specific service path (e.g., ./google-beta/services/compute) and test name (e.g., TestAccComputeInstance_basic) you wish to run.

Execution Steps

1. Verification

Verify Directory Structure

pwd # Verify we are in the generated provider directory

2. The Core Commands

Run the acceptance test with TF_LOG=DEBUG enabled, and stream the output to a log file (test_output.log) so it can be parsed later if it fails.

Execute Acceptance Test

# Replace <SERVICE_NAME> and <TEST_NAME> with the appropriate values
TF_LOG=DEBUG make testacc TEST=./google-beta/services/<SERVICE_NAME> TESTARGS='-run=<TEST_NAME>$$' > test_output.log 2>&1

3. Verification & Handoff

If the test succeeds, return to your primary workflow.
If the test fails, do NOT attempt a blind fix immediately. You MUST invoke the parse-debug-logs skill on test_output.log to understand the API failure before proposing a fix.