James Bardin

@QBY-ThimoLimpert, that sounds like the expected behavior if the resource was not created with `create_before_destroy`. The standard order of operations would be to delete the old dependency before any updates...

Hi @EugenKon, The plan renderer here is operating as designed. The HCL language doesn't have a distinct syntax for a set, but rather you would use the same `[...]` syntax...

@EugenKon, a set data structure doesn't have a key, so I'm not sure what `key: resource_record_name` would be used for. A set is an unordered collection of values, so you...

FYI this may not backport correctly and will probably need to be recreated for the v1.8 branch (both because there's currently a problem with backport-assistant, and because go.mod/go.sum always have...

Hi @gatemken, You mention that removing the `profile` entry in the provider allows the configuration to work, but the error you presented indicates there was a problem with the backend...

Hi @jbeaven2, Thanks for filing the issue! In order to inspect how exactly the cycle is connected, we will also need the associated configuration. Seeing how this is detectable during...

Since we have not heard back in a while I'm going to close the issue. If you have any updates regarding the issue, feel free to open a new issue...

Hi @michael-sterling, Thanks for filing the issue! This is an unusual consistency problem caused by changing `create_before_destroy` without allowing the resource to refresh the `create_before_destroy` value stored in the state....

Hi @yashdeored, The only way I can see you getting the result shown here is if the configuration was never applied, so there is no `aws_instance` or `private_ip` in the...

Thanks @yashdeored, If that's the case, since it does work under normal circumstances, we're going to need more detail to determine what is different in your case. What would be...