Destroying a module attempts to destroy read-only remote state too about terraform-up-and-running-code HOT 4 CLOSED

Data sources are read only. Destroying them has no effect on anything, so the actual data in S3 will be unaffected.

from terraform-up-and-running-code.

The first/only time I tried it, it failed in its attempt to destroy and hence the comment itself failed, with the typical "terraform does not roll back" warning. I am pretty sure I needed to do some manual intervention before I could continue. Sorry but I don't have the log from that saved though. Maybe I'll try again and risk it

from terraform-up-and-running-code.

I'd have to see what the error says. Again, deleting a data source should have zero effect on the underlying data, so it was probably something different.

from terraform-up-and-running-code.

@brikis98 I think you're right about this topic. I destroyed another similar set of configurations and this time it didn't error on the remote data part. The previous time must have been coincidental/unrelated. Thanks.

from terraform-up-and-running-code.