Terraform provisioners: execution and recovery limits
Provisioners run commands or other actions as part of resource lifecycle work. Those side effects can be harder to model than declarative provider resources, so the official documentation recommends treating provisioners as a last resort.
Before choosing one, check whether a provider resource, machine image, initialization mechanism or a separate configuration-management step fits the requirement. A command returning success does not necessarily establish that its external side effect is complete or repeatable.
For an unavoidable provisioner, define ownership, credentials, network reachability and a recovery path. Consider what happens if the command creates an external record and then fails before Terraform records completion. Repeating it can duplicate an operation unless the external action is idempotent.
This course does not execute provisioners, host shell commands, SSH or remote code. Its governance exercises assess the decision and recovery boundary. Read the official provisioner guidance and practice release review and recovery decisions. Real execution requires a separately authorized environment.