provider-actions

Implement imperative Terraform Provider actions at resource lifecycle events using the Plugin Framework. Terraform Actions enable imperative operations during the Terraform lifecycle. Actions are experimental features that allow performing provider operations at specific lifecycle events (before/after create, update, destroy). References: Actions follow the standard service package structure: Documentation structure: Changelog entry: Actions use the Terraform Plugin Framework with a standard schema pattern: Pay special attention to the schema definition - common issues after a first draft: Type Mismatches List/Map Element Types Computed vs Optional Validator Imports Region/Provider Attribute Nested Attributes Before submitting, verify: The Invoke method contains the action logic: Example error handling: For operations that require waiting for completion: Actions are invoked via action_trigger lifecycle blocks in Terraform configurations: Terraform 1.14.0 Supported Events: Not Supported in Terraform 1.14.0: Add sweep functions to clean up test resources: Service-Specific Prerequisites Error Pattern Matching Test Patterns Not Applicable to Actions Compile test to check for errors: Run specific action tests: Run sweep to clean up test resources: Each action documentation file must include: Front Matter Header with Warnings Example Usage Argument Reference Documentation Linting...