-
Notifications
You must be signed in to change notification settings - Fork 28
Description
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 ?