Martin Atkins

We've decided to use this issue to broadly represent all "Allow provider `for_each` to refer to [something that isn't available in early evaluation]" requests, since the technical solution to this...

Thanks for sharing that, @yshollander-selerity! I also want to capture something else I thought of when you originally shared this in Slack, for posterity: If we were to _just_ add...

Hi @FWest98! Thanks for starting this discussion. I think a crucial thing we'd need to figure out to decide the feasibility of this proposal is: can we define the `replace_triggered_by`...

I think I'd need to see a more complete example of what you have tried so far in order to suggest potential changes, but that would risk turning this issue...

I think this "types of dependency" line of thinking is a good way to summarize why it might be possible to reorder these operations so that there isn't a cycle....

Another observation I have after thinking down this path is that our _existing_ logic for changing an update into a replace if the provider reports that it cannot make a...

My sense is that the current state of this issue is in figuring out what is even possible. Without any concrete sense of what exactly it means for "replace_triggered_by to...

Thanks for sharing that example, @briantist. I don't have a ready answer yet for how to make that work given what I mentioned above about the required order of operations...

Hi @stefano-franco! Thanks for sharing the information about this. Usually support for new regions and partitions comes as an update to the AWS SDK for Go, and so we benefit...

I looked a little closer at the SDK history today and unfortunately I think the upgrade situation is quite complicated, because different parts of the SDK gained support for this...