James Bardin

[`TF_DATA_DIR`](https://developer.hashicorp.com/terraform/cli/config/environment-variables#tf_data_dir) tells terraform where to store per-working-directory data. If you change working directories then and run `init`, you are overwriting the data stored in `TF_DATA_DIR`, and will need to repeat...

Hi @bob-rohan, Thanks for filing the issue. There have been no changes in the area you are referring to between v1.2 and v1.3, so this is probably a side-effect of...

While that's definitely more resource instances than we generally see, the problem with configurations of that size is usually more associated with the sheer number of API calls that must...

That PR is related to the number of nodes being tracked during apply. The addition of [preconditions and postconditions](https://developer.hashicorp.com/terraform/language/expressions/custom-conditions) in v1.3 requires that we track all resource instances through their...

Hi @jon-grey, Thanks for filing the issue. I think we're going to need some more context in order to determine what is going on here. To start, is this run...

Hi @juicybaba, I'm not sure what the difference in structured output is, but it's not surprising that there are some differences since v1.1. That might not be directly related to...

Thanks @juicybaba. 240 resource instances is not many, so I doubt there is any impact from that alone. The only difference I can recall in v1.2 is that Terraform does...

I'm not sure yet where to look, mostly I was going to start by scanning the timestamps and see if there was any obvious place where more time was spent....

IIRC that was part of a fix to show some missing CLI UI output for data sources, but had to functional difference, nor was it changed in the log output.

The deeper look would be [here](https://github.com/hashicorp/terraform/pull/30629). It's mostly just to make sure the UI and structured run output get correct notifications about the data source operations, and overall it reduced...