Janos

That would need a separate issue and some careful consideration, not every API call is repeatable and could lead to some very expensive results if done incorrectly. Imagine dozens of...

This issue sounds to me like it's more calling for a gradual rollout of a change which would lead to an outage, less like it's intended to handle resource creation...

Hey @in0rdr is this still an issue? I'm picking up website and docs issues and I was going through the backlog of things that need doing.

Thanks for the feedback @in0rdr, I'll provisionally assign this to myself. If nobody else fixes it, I'll install Falkon and fix it within the next few weeks.

Hey @in0rdr I checked the OpenTofu website and it indeed looks broken. I have also checked a few additional websites such as [kubernetes.io](https://kubernetes.io) or the [Google Cloud front page](https://cloud.google.com/) and...

Hey @flavono123, thank you for this issue and appologies for the late reply. This sounds very similar to #306, which the core team has recently marked it as accepted and...

Having written a provider in the past, I found that a lot of the time spent isn't actually building the plan, it's the provider waiting for API calls to happen....

Hey folks, thank you very much for the issue and comments and apologies for the late reply. We have discussed this issue in the core team and feel that the...

I would argue that this should be done on a bit-by-bit basis. Creating a commit that touches all parts of the codebase will create a mess with other pending PRs...

Hey @kislerdm we have discussed this issue in the core team and decided that this refactoring would yield very little practical benefit if applied to all the existing code and...