cloudflare_address_map default_sni not applied on resource create #3692
Labels
kind/bug
Categorizes issue or PR as related to a bug.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Confirmation
Terraform and Cloudflare provider version
Terraform Version: 1.1.6
Cloudflare Provider Version: 4.37.0
Affected resource(s)
cloudflare_address_map
Terraform configuration files
Link to debug output
https://gist.github.com/edavie/55e726f9c6720617484071ef1beea88e
Panic output
No response
Expected output
When specifying the default_sni parameter within cloudflare_address_map this should be set on the address map within Cloudflare. This can be verified outside of terraform with an API call to https://api.cloudflare.com/client/v4/accounts/snip/addressing/address_maps
Which would illustrate "default_sni" being set to the value passed in the parameter for the relevant address map.
Actual output
For address map resource creates the default_sni parameter is not added to the payload (missing from https://github.com/cloudflare/terraform-provider-cloudflare/blob/v4.39.0/internal/sdkv2provider/resource_cloudflare_address_map.go#L33-L66). This is confirmed by calling the Cloudflare API directly at https://api.cloudflare.com/client/v4/accounts/snip/addressing/address_maps.
For address map resource updates the default_sni parameter is added to the payload and set properly within Cloudflare (again verifiable via Cloudflare's API). This is because update is properly referencing default_sni: https://github.com/cloudflare/terraform-provider-cloudflare/blob/v4.39.0/internal/sdkv2provider/resource_cloudflare_address_map.go#L105-L108
resourceCloudflareAddressMapCreate needs to be updated to include default_sni.
Steps to reproduce
1 - Run terraform apply to create resource, confirm no default_sni set via CF API call
2 - Re-run terraform apply to update resource (TF observes no default_sni is set on CF side), confirm default_sni is now set
Additional factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: