Open kaat-nnit opened 7 months ago
This would be nice to get resolved.
@kaat-nnit thanks for creating this issue!
We definitely agree that it would be great to fix this issue! The challenge is that it seems like it's a terraform
issue where it uses the existing values of computed attributes during terraform plan
. However, in this case, we would need to use the updated value of the computed attribute when creating a tag binding in a single terraform plan && terraform apply
.
Relevant issue: https://github.com/hashicorp/terraform/issues/28702
When schema resource is updated, terraform plan produces the following output:
Among the "# (6 unchanged attributes hidden)" there is the _schemaidentifier attribute, which does change in the apply step. This leads to some undesired behaviour in our ADO pipeline setup:
For now the easy, but more time consuming and not desirable in the long-run workaround, is to run the pipeline twice or separate the logic of managing schemas and tag binding resources in separate pipeline stages. It would be great if a change to confluent_schema resource could show the planned change to the _schemaidentifier attribute in the plan step (preferably indicating with (known after apply) ) to correctly reflect the changes to resources depending on that attribute.