-
Notifications
You must be signed in to change notification settings - Fork 966
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
Kubernetes provider gives error on first 'terraform apply' #382
Comments
This looks like wrong / missing credentials. |
Well i am providing it using a generated local-file resource. |
This seems like the upstream progressive apply issue: hashicorp/terraform#4149 You cannot currently chain together a provider's config with the output of a resource. |
could you describe token method more specific, what should i do if i choose to use token method to cert the provider |
@HanBingfeng
|
@ddska thank you for your reply : ) |
For the SA, from https://www.terraform.io/docs/providers/google/r/google_service_account_key.html: "This can be a string in the format {ACCOUNT} or projects/{PROJECT_ID}/serviceAccounts/{ACCOUNT}, where {ACCOUNT} is the email address or unique id of the service account." Since it's using a unique_id, it should use the full name. For the token, I got the suggestion from here: hashicorp/terraform-provider-kubernetes#382 (comment) Co-authored-by: Martin Petkov <mpetkov@google.com>
Hello,
Stuck with a issue on kubernetes provider.
Getting below error on first 'terraform apply'.
Everything do works perfectly fine on subsequent tf apply.
Can anyone help me to find out the reason for this.
I am working on something where I need to automate everything in my pipeline and should not fail in between like this.
Terraform Version
Terraform v0.11.11
Affected Resource(s)
Any GKE resource I try to create using the provider.
Terraform Configuration Files
Expected Behavior
It should worked on the very first time itself, instead of me manually doing a 'terraform apply' again.
More info to my case:
I am creating the kubeconfig file to a specified path using local_file resource and referring the same in my provider.
The text was updated successfully, but these errors were encountered: