James Bardin

@Xboarder56, Can you explain what you are trying to do where you need the `output` value? You can reference `triggers_replace` just like any other attribute, but if your goal is...

@apparentlymart, all config and state values are unmarked prior to calling any provider method because the protocol cannot serialized marks. Perhaps stripping and re-applying marks could be pushed out into...

@Xboarder56 what I was describing would look more like below. There is no reason to actually pass the value through input/output here, you are only concerned with triggering replacement based...

Thanks @Xboarder56, I think we can leave this here for now, to take a closer look if there is any possibility of adding this type of value handling to the...

Note that `terraform_data` is not a special case right now, it follows the same internal protocol as any other managed resource. Making it a special case would be unprecedented, and...

Hi @archoversight, Thanks for filing the issue. Terraform already does what you describe, or at least that is the intended behavior. Can you show an example where non-dependent resources are...

I'm still not certain we're talking about the same issue here. Take this excessively contrived example: ``` resource "null_resource" "fail" { provisioner "local-exec" { command = "exit 1" } }...

Thanks @archoversight, I see what you're getting at now. Terraform manages dependencies at the resource level, not between individual instances. This means that while some of `null_resource.maybe_fail` may have succeeded,...

This sounds reasonable to me. My only comment so far would be to name it something like `local_forward` to align it with the actual type of forwarding being done (`-L`),...

Hi @dmrzzz, Refinements serve a different purpose than references. Dependencies are handled via static references in the configuration, not the value derived from the expressions containing the references. Taking your...