James Bardin

Oh, that's not from a `moved` block, that is from a `removed` block. The "will not be destroyed" is extremely important, probably just as much as being destroyed for some...

Hi @frankcaoyun, Thanks for filing the issue. This is a bit of a rough spot in the state management, as the user-facing interface for dealing with changes is intended to...

Thanks @frankcaoyun. If I understand correctly, you want to simultaneously reduce the number of instances of a resource while also changing `create_before_destroy`? I could see that as being a hole...

Hi @tomelliot16, Thanks for filing the issue. Can you supply a configuration to reproduce the issue? Without a minimal reproducible example it's going to be difficult to pinpoint what might...

Hi @tomelliot16, Thanks for the example. The issue was created referencing v1.13.5, but your repro here uses v0.13 and v0.14. Those are very old versions of Terraform, and don't represent...

Note that it's not surprising that this doesn't work, I wouldn't expect it to. What I'm more interested in is if there was some form of this which recently stopped...

> │ data.aws_servicequotas_service_quota.servicequotas will be known only after apply > this statement shouldn't be true. the data source is known before apply and a terraform plan also works without any...

Closing for now. If a reproduction which shows a regression between v1.13 and v1.14 is found, feel free to add it here for further review, or file a new issue....

Hi @hobbyhorse, Terraform doesn't really have a concept of "drift" to begin with, so that might be part of the confusion. Terraform does note when changes have been made outside...

Thanks @hobbyhorse. So if I understand correctly, what you mean by "enforce changes" is that you would only want to apply changes when the config itself has changed? That isn't...