James Bardin

Hi @jbg, Thanks for filing the issue. Without any configuration or logging there's not much to go by here. Would it be possible to create a more minimal reproduction, or...

Thanks @jbg, this cycle looked very much like what the linked PR handles, so I linked them. They may still be related, but I'll reopen this for further investigation.

Would it be possible to compare trace logs from a plan in each version? You can avoid all the provider output by using `TF_LOG_CORE=trace`, though it's still going to be...

Prior to v1.3 the apply graph could discard most of the objects entirely, which simplified things greatly and avoided problems with use cases like this. Basically the dependencies were there,...

Hi @skeswani, thanks for filing the issue. There are a couple reasons this is happening now, because of how output changes are planned, and how they are ordered to prevent...

Hi @yherve, It appears that your provider is returning a nil value for a resource block schema, which Terraform is not expecting to handle. The fix in Terraform should be...

Hi @jcollum, Thanks for filing the issue, I can see how this might be confusing. The `-backend` flag for `init` determines if the backend is going to be configured or...

Hi @dmrzzz, Thanks for filing the issue! I think the surprising part of the cycle here is actually that it is avoidable with your second case. The cycle can be...

Thanks @dmrzzz. I understand what you are saying, but from the language perspective we have to initially assume that any module which contains `count` or `for_each` could have dependencies that...

Hi @SennaSemakula, Thanks for filing the issue. I'm not able to reproduce this, do you have any more information about the configuration or events that let up to the crash,...