-
Notifications
You must be signed in to change notification settings - Fork 626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TF13: data.cloudflare_zones reports changes on every plan #764
Comments
Thanks for this; For now, let's see if this gets addressed in 0.13.x core instead of each provider and if it doesn't we can look to update this within the provider itself. |
Same issue with Terraform 0.13.2. |
Hi! If I'm not mistaken, they patched something similar on the core side in June (hashicorp/terraform#25302). |
+1 We're running into this too. |
@jacobbednarz This does not seem to be backported to |
For the data sources where we have multiple values returned, we'll need to ensure we take all of the IDs, join them and hash the value. If we don't do that, the provider won't ever update the ID in the event changes are present on the remote APIs end. By the looks of things, all of the provider data sources are impacted by this. |
add support for Cloudflare Images
Terraform Version
Terraform v0.13.0
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Repeated plans should report no changes.
Actual Behavior
Every plan shows a change for the data source:
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
terraform init
terraform plan -out terraform.plan
terraform apply terraform.plan
terraform plan
References
This looks like basically the same issue as hashicorp/terraform-provider-aws#14579?
The text was updated successfully, but these errors were encountered: