Skip to content
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

cloudflare_snippet import state write error #4777

Open
3 tasks done
luca-bozzetto-depop opened this issue Dec 16, 2024 · 2 comments
Open
3 tasks done

cloudflare_snippet import state write error #4777

luca-bozzetto-depop opened this issue Dec 16, 2024 · 2 comments
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.

Comments

@luca-bozzetto-depop
Copy link

luca-bozzetto-depop commented Dec 16, 2024

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

Cloudflare terraform provider v4.48.0

cloudflare_snippet.headers_transforms: Importing from ID "<zone-id>/<snippet-name>"...
╷
│ 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

Affected resource(s)

cloudflare_snippet

Terraform configuration files

resource "cloudflare_snippet" "my_snippet" {
  zone_id  = "zone-id"
  name = "snippet-name"
  main_module = "file.js"
  files {
    name = "file.js"
    content = file("file.js")
  }
}

Link to debug output

https://gist.githubusercontent.com/luca-bozzetto-depop/80f12bab2c83f55b7b32668dad4a6e31/raw/5a8f3253aca0a0ef17b949c7b1c85d55ff0c2e60/cloudflare_snippet_import_error

Panic output

No response

Expected output

Import successful!

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. create a snippet in your cloudflare zone
  2. add the corresponding cloudflare_snippet resource to your terraform state
  3. use the zone-id and snippet name and run a terraform import `terraform import cloudflare_snippet.my_snippet /
  4. import fails

Additional factoids

No response

References

No response

@luca-bozzetto-depop luca-bozzetto-depop added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 16, 2024
Copy link
Contributor

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 github-actions bot added triage/needs-information Indicates an issue needs more information in order to work on it. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 16, 2024
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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.
Projects
None yet
Development

No branches or pull requests

1 participant