James Bardin

While in our experience most resources can be made to work with `create_before_destroy`, yes it is possible that there may be resources unable to support that ordering. Not being able...

Hi @scott-doyland-burrows, Terraform doesn't run sentinel or know anything about its policies, so there's not really any way for it to control the output. I'm guessing you are using the...

A recent duplicate led me to a clearer reproduction. The failure here is during the refresh walk, which is partially driven by the configuration. Because data sources need to be...

Hi @jnixon-blue, The issue here is a case where an invalid root module output configuration cannot be applied, and since `destroy` is an implied apply operation, it requires fixing the...

Hi @staranto, Thanks for filing the issue! That sentence should probably indicate that the "state" which you have access to is scoped to the root module. The expression syntax cannot...

Hi @lijok, Thanks for filing the issue. The `providers lock` command can't create a complete lock file from the cache, since it does not contain the hashes for all architectures,...

Hi @EugenKon, State refactoring operations can only affect the state, they cannot make API calls because we can't start planning until after the state has been updated to match the...

Yes, in this case the `moved` block would produce a warning like ``` │ Terraform tried to adjust resource instance addresses in the prior state based on change information recorded...

Closing since we have a working solution for now. Exceptional situations will still tend to require use of the CLI, and it's not always going to be a single command...

Since we have not heard back in a while I'm going to close the issue. If you have any updates regarding the issue, feel free to open a new issue...