-
Notifications
You must be signed in to change notification settings - Fork 609
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_account_member resource does not properly support account_id provider deprecation #1819
Comments
Thank you for reporting this issue! For maintainers to dig into issues it is required that all issues include the entirety of This issue has been marked with |
Also seeing this same behavior trying to move account_members to using account_id. |
thanks for raising this @JDKnobloch. looking through the history, it looks like the commit that actually made use for creation and deletion was dropped during a merge conflict. i've gone ahead and pulled it into #1823 so this should work now. feel free to pull that branch locally, build a custom version of the provider and give it a while to make sure it works for you too. |
This functionality has been released in v3.21.0 of the Terraform Cloudflare Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
@jacobbednarz It's still happening with |
This is not resolved, Also still happening for me on |
Still having the issue as weill w/ terraform |
This is still the same with |
Hello, does anyone have a valid workaround for this at all? I tried the workaround listed here which does not seem to work for me:
|
Still getting the same issue on V4.21.0 of provider, 1.6.6 of terraform. |
Confirmation
Terraform and Cloudflare provider version
Terraform:
v1.2.6
Cloudflare provider:
v3.20.0
Hey all - we have gone ahead and began migrating away from supplying the
account_id
variable within the provider and have noticed that thecloudflare_account_member
resource does not properly work using the providedaccount_id
variable on the resource level.An issue tracker exists that marks the work as complete for this resource, however, the
account_id
variable does not appear to work. Example below includes the failed plan output.Affected resource(s)
Terraform configuration files
Debug output
cloudflare_account_member.example: Refreshing state... [id=0be7de180d632439373b8aedb0ba75f3]
2022-08-04T15:22:21.834-0600 [ERROR] vertex "cloudflare_account_member.example" error: required missing account ID
2022-08-04T15:22:21.834-0600 [ERROR] vertex "cloudflare_account_member.example" error: required missing account ID
2022-08-04T15:22:21.835-0600 [ERROR] vertex "cloudflare_account_member.example(expand)" error: required missing account ID
2022-08-04T15:22:21.835-0600 [ERROR] provider.terraform-provider-cloudflare_v3.20.0: Response contains error diagnostic: @module=sdk.proto diagnostic_summary="required missing account ID" tf_proto_version=5.3 tf_provider_addr=registry.terraform.io/cloudflare/cloudflare tf_resource_type=cloudflare_account_member tf_rpc=ReadResource @caller=github.com/hashicorp/[email protected]/tfprotov5/internal/diag/diagnostics.go:56 diagnostic_detail= diagnostic_severity=ERROR tf_req_id=9ab96701-a515-4641-0ab4-199b3f56300f timestamp=2022-08-04T15:22:21.834-0600
Panic output
No response
Expected output
No changes - this resource already exists, we simply moved the
account_id
from provider to resourceActual output
│ Error: required missing account ID
│
│ with cloudflare_account_member.example,
│ on user.tf line 4, in resource "cloudflare_account_member" "example":
│ 4: resource "cloudflare_account_member" "example" {
Steps to reproduce
Have not fully verified a from scratch
cloudflare_account_member
resource, our general steps were:cloudflare_account_member
resource using provider-suppliedaccount_id
account_id
and use instead resource-suppliedaccount_id
Additional factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: