Martin Atkins

The way I've understood this request is to make it possible to exclude certain kinds of changes from a plan while still performing other changes. The existing `-target` [planning option](https://opentofu.org/docs/cli/commands/plan/#planning-options)...

Hi @Gerthum, I think you are proposing to add a new planning option that would cause OpenTofu to make `prevent_destroy` mean "skip instances of this resource if their planned action...

Ahh, okay. Here's what I've understood now: You have written your main module code to set `prevent_destroy = true` to force the plan phase to fail if instances of certain...

One hazard we need to watch for if we try to generalize this request to _all_ action types is that actions can depend on one another, and so we'd need...

I did some light prototyping today about _just_ the idea of taking a digest of the "desired state" (configuration value) for a resource instance. I found two interesting things that...

I think unfortunately this issue got "stuck" in much the same way that the Terraform one did: it was describing a valid problem, but framing it in terms of a...

If "the halting problem" was intended to refer to the possibility that a multi-stage plan/apply might never reach a converged state no matter how many rounds you run: Indeed, it's...

We can potentially discuss ways to react in a more automatic way to these new `-exclude` suggestions, but given that we don't even know yet whether this mechanism will be...

The idea of setting a particular input variable as _entirely_ unknown, using options like `-var-unknown` or such, would get _most_ of the way there and so could well be sufficient...

Reacting to the prototype above, I wonder if it would be reasonable to say that unknown input variables are _only_ allowed for `tofu plan` (not for `tofu apply`) and that...