Importing a cloudflare_list is not possible without the inline items

[mariusmanea-selfridges]

Confirmation

• My issue isn't already found on the issue tracker.
• I have replicated my issue using the latest version of the provider and it is still present.

Terraform and Cloudflare provider version

Terraform v1.8.0
on darwin_arm64

• provider registry.terraform.io/cloudflare/cloudflare v4.29.0
• provider registry.terraform.io/hashicorp/aws v5.45.0
• provider registry.terraform.io/hashicorp/null v3.2.2

Affected resource(s)

cloudflare_list

Terraform configuration files

resource "cloudflare_list" "example" {
  account_id  = "f037e56e89293a057740de681ac9abbe"
  name        = "example_list"
  description = "example IPs for a list"
  kind        = "ip"
}

Link to debug output

https://gist.github.com/

Panic output

No need for debug output, the issue can be reproduced by anyone.

Expected output

when running:
terraform import cloudflare_list.example <account_id>/<list_id>
should be possible without importing the list items in this object, because I would like to manage the list items separately, using the cloudflare_list_item resource, and import those items separately.

Actual output

Importing the cloudflare_list resource brings along all the list_items with it, which I cannot remove from this object afterwards, so I can manage them separately using cloudflare_list_item resource.
The import command should have a flag (import_items = true/false) which should decide when to import the items or not.

Steps to reproduce

1. Create a list_item resource
2. Import the existing resource from the environment
3. Note that the imported resource contains the list_items, which we don't want.

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.

[mariusmanea-selfridges]

There's no need for the debug log, the issue is self-explanatory.
It is not currently possible (as far as I know) to import a cloudflare_list, without importing the list_items along with it.
But since cloudflare provider allows managing cloudflare_list_item resource separately, it should be possible to import an empty cloudflare_list, and then import each cloudflare_list_item individually.

[mariusmanea-selfridges]

BTW, for anyone interested:
To get this working, I edited the tfstate json file manually (to remove the items[] list from the clouflare_list resource) and then I re-uploaded it to the s3 bucket.
Also, I had to update the md5 for the state file in the DynamoDB table.

[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.