-
Notifications
You must be signed in to change notification settings - Fork 548
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
vault_generic_secret fails to read secrets (unexpected EOF) #1
Comments
From what I can tell, this is no longer an issue. For example, running data "vault_generic_secret" "test" {
path = "secret/hello"
}
output "secret" {
value = "${data.vault_generic_secret.test.data.recipient}"
} outputs data "vault_generic_secret" "test" {
path = "secret/hello"
}
output "secret" {
value = "${data.vault_generic_secret.test.data}"
} outputs
I'm going to close this issue out, but if this is not what people were expecting, or is still unclear, or I misunderstood the problem, please don't hesitate to comment on this issue or open a new one. |
@paddycarver I am running into this problem with 0.11.0. This has corrupted my state at this point as well. Any ideas on how to fix? Even the |
Hey @rossedman, sorry to hear that. What version of the Vault provider are you using? |
Hi everyone, I'm going to close this out, as I can't seem to get a reproduction, and nobody's chimed in with details in some time. If you're still experiencing this issue, I'd love an issue opened containing the following:
Thanks! |
merge upstream into fork
Added support for wrapped token creation.
aws_secret_backend_role: support role_arns argument
* Rush B! * . * Provider config (#1) * Rush B! * . * added provider_config to the matchingJwtMountConfigOptions list
merge upstream into fork
Added support for wrapped token creation.
aws_secret_backend_role: support role_arns argument
merge from upstream
* Rush B! * . * Provider config (hashicorp#1) * Rush B! * . * added provider_config to the matchingJwtMountConfigOptions list
fix: handle Token expiration
This issue was originally opened by @IevgenKabanets as hashicorp/terraform#10999. It was migrated here as part of the provider split. The original body of the issue is below.
Terraform Version
Terraform v0.8.2
Affected Resource(s)
Please list the resources as a list, for example:
Terraform Configuration Files
Debug Output
https://gist.github.com/IevgenKabanets/c16d2e5ef4520921ba05e5a79ee11079
Panic Output
https://gist.github.com/IevgenKabanets/c16d2e5ef4520921ba05e5a79ee11079
Expected Behavior
The secret should be read, as it's present in Vault and accessible with
curl
.Actual Behavior
Crashed with
* data.vault_generic_secret.docker: unexpected EOF
Steps to Reproduce
export VAULT_TOKEN=<root_token or any token>
terraform plan
orterraform apply
Important Factoids
This works fine
Also, the error is gone once I read full path to entry (secret/docker/docker_registry_pwd)
which seems to be wrong, as
vault_generic_secret
should return a map with possible keys/values.References
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:
The text was updated successfully, but these errors were encountered: