-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
google_gke_hub_feature_membership fails apply with a 404 error #20847
Comments
Looking in the terraform registry documentation (link here) and in the error message you have to use a
I've tried with the terraform registry example adapting the code to yours and had no errors |
Hi @ggtisc, thanks for your support here. After trying with your suggestion, I get this error:
on the first I tried with a second apply, and it worked. Strange. Let me see if I can capture a debug log. Update: the |
Try with this example and then change names and variables according to your needs:
|
Community Note
Terraform Version & Provider Version(s)
Terraform v1.5.7
on
Same results with the following versions of both GA and beta providers: v6.9.0, v6.12.0
Affected Resource(s)
google_gke_hub_feature_membership
Terraform Configuration
Debug Output
Working on getting this because once I configured the membership manually, I wasn't able to reproduce the issue.
Expected Behavior
terraform apply
to succeed.Actual Behavior
Got this error when running
terraform apply
:Steps to reproduce
terraform apply
against that projectImportant Factoids
google_gke_hub_feature_membership
arguments are correct. I double checked them using thegcloud container hub memberships list
command.google_gke_hub_feature_membership
is correct. I validated this by doing the following:gcloud container fleet mesh update --management automatic --memberships cluster-name --location global
google_gke_hub_feature_membership
in the Terraform stateterraform plan
doesn't report any change against thegoogle_gke_hub_feature_membership
resource.google_gke_hub_feature_membership
starts working as expected.References
No response
The text was updated successfully, but these errors were encountered: