terraform taint command informs Terraform that a particular object has
become degraded or damaged. Terraform represents this by marking the
object as "tainted" in the Terraform state, and Terraform will
propose to replace it in the next plan you create.
Warning: This command is deprecated. For Terraform v0.15.2 and later, we recommend using the
-replace option with
terraform apply instead (details below).
For Terraform v0.15.2 and later, we recommend using the
-replace option with
terraform apply to force Terraform to replace an object even though there are no configuration changes that would require it.
$ terraform apply -replace="aws_instance.example"
We recommend the
-replace option because the change will be reflected in the Terraform plan, letting you understand how it will affect your infrastructure before you take any externally-visible action. When you use
terraform taint, other users could create a new plan against your tainted object before you can review the effects.
$ terraform taint [options] <address>
address argument is the address of the resource to mark as tainted.
The address is in
the resource address syntax,
as shown in the output from other commands, such as:
aws_instance.baz[\"key\"](quotes in resource addresses must be escaped on the command line, so that they will not be interpreted by your shell)
This command accepts the following options:
-allow-missing- If specified, the command will succeed (exit code 0) even if the resource is missing. The command might still return an error for other situations, such as if there is a problem reading or writing the state.
-lock=false- Disables Terraform's default behavior of attempting to take a read/write lock on the state for the duration of the operation.
-lock-timeout=DURATION- Unless locking is disabled with
-lock=false, instructs Terraform to retry acquiring a lock for a period of time before returning an error. The duration syntax is a number followed by a time unit letter, such as "3s" for three seconds.
For configurations using the Terraform Cloud CLI integration or the
remote backend only,
also accepts the option
For configurations using
local backend only,
terraform taint also accepts the legacy options