cloudflare_cloud_connector_rules cannot be imported due to a schema error

[willh-airia]

Confirmation

• This is a bug with an existing resource and is not a feature request or enhancement. Feature requests should be submitted with Cloudflare Support or your account team.
• I have searched the issue tracker and my issue isn't already found.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

(⎈|airia-cluster-staging:default)❯ terraform -v
Terraform v1.8.5
on darwin_arm64

• provider registry.terraform.io/cloudflare/cloudflare v4.41.0

Affected resource(s)

cloudflare_cloud_connector_rules

Terraform configuration files

import {
  id = "myZoneId/myConnectorRuleId"
  to = cloudflare_cloud_connector_rules.example
}

resource "cloudflare_cloud_connector_rules" "example" {
  zone_id = myZoneId

  rules {
    description = "A Description"
    enabled     = true
    expression  = "An Expression"
    provider    = "azure_storage"
    parameters {
      host = "An Azure Storage Account URL"
    }
  }
}

Link to debug output

None

Panic output

No response

Expected output

Terraform imports the resource into the state, which can then be modified by the Terraform resource.

Actual output

│ Error: State Write Error
│
│ An unexpected error was encountered trying to retrieve type information at
│ a given path. This is always an error in the provider. Please report the
│ following to the provider developer:
│
│ Error: AttributeName("id") still remains in the path: could not find
│ attribute or block "id" in schema

Steps to reproduce

1. Manually create a Cloudflare Connector Rule
2. Get the ID and attempt to import to an existing cloudflare_cloud_connector_rules resource
3. Run terraform plan

Additional factoids

I can see that the id field is not set in schema.go: https://github.com/cloudflare/terraform-provider-cloudflare/blob/2b31cd68588ec82a373175a1d55a6d163e366a48/internal/framework/service/cloud_connector_rules/schema.go

References

No response

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

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.

[github-actions]

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]

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