-
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
provider overrides provided token if running inside a pod #787
Comments
Hi, this is fixed since the v1.11.0 release. Get v1.11.1 though, it's better. |
Ah, okay, will try. Thanks! Closing issue. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 hashibot-feedback@hashicorp.com. Thanks! |
Terraform Version
0.12.13
Affected Resource(s)
Terraform Configuration Files
Debug Output
https://gist.github.com/mrferos/610ed1ccea8d0e2845966dd9291eff62
Panic Output
N/A
Expected Behavior
I would expect for the provided token to be used
Actual Behavior
Because this was running inside a kubernetes pod
KUBERNETES_SERVICE_HOST
andKUBERNETES_SERVICE_PORT
were defined, the provided token was ignored and it picked up the service account token in the pod.Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Important Factoids
My quick workout was just to prepend
KUBERNETES_SERVICE_HOST="" KUBERNETES_SERVICE_PORT=""
toterraform apply
andterraform plan
References
N/A
The text was updated successfully, but these errors were encountered: