-
Notifications
You must be signed in to change notification settings - Fork 29
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
vaultenv 0.13.3 and Hashi Corp hosted vault #111
Comments
Hi @raiknet, We haven't used Vaultenv with Hashicorp's hosted Vault service yet and it seems that this is not possible with the current version of Vaultenv. I think that this error is due to Vaultenv not being namespace-aware: Vault on HCP seems to depend on Vault's namespacing feature. Vaultenv currently does not pass the I think that it shouldn't be too hard to make Vaultenv namespace-aware: if I'm not mistaken the required steps would be to
We currently aren't using Vault on HCP, so adding namespace support is not currently a priority for us. We would probably accept a PR that adds namespace support though :) |
I worked successfully with vaultenv in my dev environment. Now I switched to Hashi Corp enterprise hosted vault and I get "Invalid Vault token". I verified the token multiple times and it works when I use the vault native command " vault kv ..." . I try to switch to a non TLS connection than I get a "[ERROR] Received bad JSON from Vault: Error in $: Failed reading: not a valid json value" . Here is my debug:
Host: vault-cluster.vault.2cxxxxxxxx2bb.aws.hashicorp.cloud
Port: 8200
Addr: https://vault-cluster.vault.xxxxx43-9601-cf54xxx32bb.aws.hashicorp.cloud:8200
Token: *****
Secret file: ./vaultenv-aws
Command: env
Arguments: []
Use TLS: True
Validate certs: True
Inherit env: True
Inherit env blacklist: []
Base delay: 40
Retry attempts: 9
Log-level: Info
Use PATH: True
Concurrent requests: 8
Do I miss something ? Should version 0.13.3 work with no issues with the Hashi corp hosted vault ?
The text was updated successfully, but these errors were encountered: