chrismarget-j

Thought I was experiencing something similar to the OP, now think it's more likely I misunderstood the mechanisms at work. This comment edited into a no-op.

There's discussion [here](https://discuss.hashicorp.com/t/cooping-with-parallelism-is-there-a-way-to-prioritise-resource-types/55690) about solving a problem like this using a provider-managed `sync.Mutex`. Would that solve the problem without requiring any changes to the schema? If something like `Sequential` were...

> You're example isn't quite what I'm trying to solve for: > > * To prevent concurrent operations of the SAME resource (aka multiple instances of resource A in the...

This will be super helpful. I'm looking forward to it being available. When a plan is being generated, will the state value be used in place of a value picked...

I'm looking forward to support for ephemeral resources/values, but mostly because of their relationship with terraform 1.11's write-only attributes. These two features together will be a huge improvement to the...

> what if a module is deployed with opentofu, then the module is updated to use ephemeral resources I'd expect that to fail.

Attribute-based expressions of semantic equality behavior sound pretty interesting to me as a provider developer. I don't have any use cases in mind, but expect I'd find 'em if it...

I've often wished that the `attr.Value` interface included a `HasValue() bool` method for the same reason. > think I can safely assume the plan will never be an `Unknown` value...