terraform taint null_resource doesn't work anymore (v0.7.x).

[lesaux]

It seems terraform taint null_resource doesn't work in v0.7.1 anymore (I'm using Terraform v0.7.1-dev).

resource "null_resource" "some_command" {

    provisioner "remote-exec" {
        connection {
            host = "somehost"
            user = "someUser"
        }
        inline = [
          "sudo docker run -d --restart=always -p 8080:8080 someimage
        ]
    }

}

$ terraform taint null_resource.some_command
The resource null_resource.some_command in the module root has been marked as tainted!
$ terraform plan
...
null_resource.some_command: Refreshing state...
...
No changes. Infrastructure is up-to-date. This means that Terraform
could not detect any differences between your configuration and
the real physical resources that exist. As a result, Terraform
doesn't need to do anything.

[afritzler]

Same issue here. I am on terraform 0.7.0.

[phinze]

Thanks for the report! This is fixed in #8167 which will come out with v0.7.1 due out next week. 👍

[hashibot[bot]]

I'm going to lock this issue because it has been closed for _30 days_ ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.