provider-actions

Define a Schema method with framework attribute types, then implement an Invoke method that reads config, creates the provider client, reports progress, and handles errors via diagnostics. Register the action in the service package and add tests, docs, and a changelog entry.

Use an action_trigger block inside a resource's lifecycle block, referencing the action and specifying events like after_create or after_update. Terraform 1.14.0 supports before_create, after_create, before_update, and after_update events.

Terraform 1.14.0 supports before_create, after_create, before_update, and after_update events. The before_destroy and after_destroy events are not supported and will cause validation errors if used.

Type mismatches usually come from mixing framework types like fwtypes.String with plugin-framework types like types.String in model structs. Also ensure List and Map attributes define ElementType, and run go build to catch remaining type errors.

Write acceptance tests using resource.TestCase with ProtoV5ProviderFactories and a TerraformVersionCheck skipping below 1.14.0. Run them with TF_ACC=1 go test, and add sweep functions to clean up test resources prefixed with tf-acc-test.