Invalid Configuration for Read-Only Attribute

[rfdrew]

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

terraform -v
Terraform v1.10.4
on darwin_amd64

• provider registry.terraform.io/cloudflare/cloudflare v5.0.0-rc1

Affected resource(s)

cloudflare_account_token

Terraform configuration files

resource "cloudflare_account_token" "terraform" {
  provider = cloudflare.token_create
  account_id = data.cloudflare_account.example.id
  name = "Terraform"
  policies = [{
    effect = "allow"
    permission_groups = [
      {
        id = "3030687196b94b638145a3953da2b699",
        name = "Zone Settings Write"
      }
    ]
    resources = {
      "com.cloudflare.api.account.${data.cloudflare_account.example.id}" = "*"
    }
  }]
}

Link to debug output

none

Panic output

With "name" attribute

% terraform apply -target=cloudflare_account_token.terraform
╷
│ Error: Invalid Configuration for Read-Only Attribute
│ 
│   with cloudflare_account_token.terraform,
│   on cloudflare-account-tokens.tf line 1, in resource "cloudflare_account_token" "terraform":
│    1: resource "cloudflare_account_token" "terraform" {
│ 
│ Cannot set value for this attribute as the provider has marked it as read-only. Remove the configuration line setting the value.
│ 
│ Refer to the provider documentation or contact the provider developers for additional information about configurable and read-only attributes that are supported.
╵
╷
│ Error: Invalid Configuration for Read-Only Attribute
│ 
│   with cloudflare_account_token.terraform,
│   on cloudflare-account-tokens.tf line 4, in resource "cloudflare_account_token" "terraform":
│    4:   name = "Terraform"
│ 
│ Cannot set value for this attribute as the provider has marked it as read-only. Remove the configuration line setting the value.
│ 
│ Refer to the provider documentation or contact the provider developers for additional information about configurable and read-only attributes that are supported.
╵

Without "name" attribute

% terraform apply -target=cloudflare_account_token.terraform
╷
│ Error: Missing required argument
│ 
│   on cloudflare-account-tokens.tf line 1, in resource "cloudflare_account_token" "terraform":
│    1: resource "cloudflare_account_token" "terraform" {
│ 
│ The argument "name" is required, but no definition was found.
╵

Expected output

Account token will be created

Actual output

Error: Invalid Configuration for Read-Only Attribute or Error: Missing required argument

Steps to reproduce

Use "name" attribute in "cloudflare_account_token" resource

Additional factoids

No response

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.