provider-actions

To implement imperative Terraform provider actions, use the Plugin Framework to scaffold a new action implementation by defining the required Invoke method and schema within your provider service package to execute custom logic during lifecycle events.

Yes, you can execute custom logic during Terraform lifecycle events by implementing imperative provider actions. This allows you to trigger external API calls or complex state-validation logic immediately after a resource is provisioned but before the operation completes.

Yes, implementing imperative provider actions provides built-in mechanisms for real-time progress reporting and timeout management, ensuring robust error handling and feedback during long-running infrastructure-as-code operations.

Triggering imperative provider actions requires Terraform 1.14.0 or higher. The implementation ensures compliance with these trigger event standards and schema validation requirements to execute custom lifecycle logic properly.

You scaffold a new provider action by defining the required Invoke method and schema within your provider service package. This structure facilitates provider-specific operations that require progress reporting and robust error handling.