Hi there! vault status is an unauthenticated endpoint, so it could be that you’ve set the Vault token environment variable incorrectly, because your kv put command looks correct to me.
Try:
# In TTY1
VAULT_DEV_ROOT_TOKEN_ID=root vault server -dev
# In TTY2
export VAULT_ADDR=http://127.0.0.1:8200
export VAULT_TOKEN=root
vault kv put secret/hello foo=world
I’ve just run it and it works for me. Note that you don’t need to set the root token via VAULT_DEV_ROOT_TOKEN_ID, but it just helps me provide a complete example script.
Glad to hear it! I’m not sure to be honest, but the permission error you saw was at the Vault API application level, so shouldn’t be related to any file system/UNIX permissions.
Now that I understand Vault a bit better… When using the -dev option, everything is stored in memory, and not mounted to the file-system, so any permissions errors that come up are most likely a result of a type=o in the access key.