You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are experiencing an issue with the Confluent provider where terraform tries to recreate all the resources if there is a dependency on a data block.
Here is an example:
The following code creates a service account and identity pool, and assigned them some schema-registry level permissions.
But due to the data blocks inside the rbac-schema-registry.tf file if I try to add another service account or identity pool in my .tfvars file, terraform will try to redeploy all the rbac permissions as it is re-running the data block and doesn't know what the output of it is at the plan step, as seen below.
Is it possible to resolve this issue so that we can run data blocks inside modules without having to redeploy everything in that module?
Hi all,
We are experiencing an issue with the Confluent provider where terraform tries to recreate all the resources if there is a dependency on a data block.
Here is an example:
The following code creates a service account and identity pool, and assigned them some schema-registry level permissions.
But due to the data blocks inside the
rbac-schema-registry.tf
file if I try to add another service account or identity pool in my .tfvars file, terraform will try to redeploy all the rbac permissions as it is re-running the data block and doesn't know what the output of it is at the plan step, as seen below.Is it possible to resolve this issue so that we can run data blocks inside modules without having to redeploy everything in that module?
main.tf:
rbac-schema-registry.tf
file:Plan: 4 to add, 0 to change, 3 to destroy.
The text was updated successfully, but these errors were encountered: