terraform-provider-vault
terraform-provider-vault copied to clipboard
Provider keeps Eating my Kubernetes Cluster Auth Methods
Hi there,
Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.
Terraform Version
Run terraform -v
to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
Affected Resource(s)
Please list the resources as a list, for example:
- vault_kubernetes_auth_backend_config
If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.
Terraform Configuration Files
Will add later
Debug Output
Please provider a link to a GitHub Gist containing the complete debug output: https://www.terraform.io/docs/internals/debugging.html. Please do NOT paste the debug output in the issue; just paste a link to the Gist.
Will add later.
Panic Output
If Terraform produced a panic, please provide a link to a GitHub Gist containing the output of the crash.log
.
Will add later.
Expected Behavior
What should have happened?
What should have happened is that the provider should have been able to import the state for Kubernetes Auth Methods while still allowing us to configure roles.
Actual Behavior
What happened instead was that this provider updated both the auth methods AND roles after state import, removing the Token Reviewer JWTs from the Kubernetes Auth Method.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
- Create an auth method for Kubernetes, and several auth roles for it.
- Import the state for the auth method and the roles
- Push a change to the role
- Watch none of your auth methods imported this way work. At all.
Important Factoids
This was a vanilla, typical Kubernetes Auth method setup.
References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
- GH-1234 We can refer to some support requests we've made elsewhere, but no other Github Issues that I know of.