cloudflare / terraform-provider-cloudflare

Cloudflare Terraform Provider
https://registry.terraform.io/providers/cloudflare/cloudflare
Mozilla Public License 2.0
754 stars 576 forks source link

SRV data fields 'service', 'proto' and 'name' are no longer supported #3502

Closed avx-rodmans closed 6 days ago

avx-rodmans commented 1 month ago

Confirmation

Terraform and Cloudflare provider version

Terraform v1.7.0
on linux_arm64
+ provider registry.terraform.io/cloudflare/cloudflare v4.38.0
+ provider registry.terraform.io/hashicorp/aws v5.59.0

Affected resource(s)

Terraform configuration files

resource "cloudflare_record" "cloudflare_record" {
  name            = "record_01"
  comment         = "<comment>"
  zone_id         = "<zone_id>"
  allow_overwrite = false

  data {
    service  = "_https"
    proto    = "_tcp"
    name     = "somename.domain.com"
    priority = 5
    weight   = 0
    port     = 8443
    target   = "somename.domain.com"
  }
}

Link to debug output

cannot-include

Panic output

na

Expected output

Resource created

Actual output

Error: failed to create DNS record: SRV data fields 'service', 'proto' and 'name' are no longer supported. Please see <https://developers.cloudflare.com/fundamentals/api/reference/deprecations/#name-related-data-fields-on-srv-dns-records> for more information. (9000)
│ 
│   with cloudflare_record.cloudflare_record["record_01"],
│   on main.tf line 5, in resource "cloudflare_record" "cloudflare_record":
│    5: resource "cloudflare_record" "cloudflare_record" {

Steps to reproduce

  1. Use service, name, and proto in the data block

Additional factoids

According to documentation here, these are deprecated in the API however have not been updated in the provider.

References

No response

github-actions[bot] commented 1 month ago

Community Note

Voting for Prioritization

Volunteering to Work on This Issue

github-actions[bot] commented 1 month ago

Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of TF_LOG=DEBUG output to be provided. The only parts that should be redacted are your user credentials in the X-Auth-Key, X-Auth-Email and Authorization HTTP headers. Details such as zone or account identifiers are not considered sensitive but can be redacted if you are very cautious. This log file provides additional context from Terraform, the provider and the Cloudflare API that helps in debugging issues. Without it, maintainers are very limited in what they can do and may hamper diagnosis efforts.

This issue has been marked with triage/needs-information and is unlikely to receive maintainer attention until the log file is provided making this a complete bug report.

jacobbednarz commented 1 month ago

this is already under way via #3286

github-actions[bot] commented 1 week ago

Marking this issue as stale due to 30 days of inactivity. This helps our maintainers find and focus on the active issues. If this issue receives no comments in the next 7 days it will automatically be closed. Maintainers can also remove the lifecycle/stale label. If this issue was automatically closed and you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thank you!

github-actions[bot] commented 6 days ago

This issue was closed because it has been stalled for 7 days with no activity.