Running the second command in the GUI CLI will succeed.
Running the second command in the GUI CLI will fail. The second command is vault kv put secret/creds passcode=my-long-passcode. This command attempts to write a secret named creds with the value passcode=my-long-passcode to the secret path, which is the default path for the kv secrets engine. However, the kv secrets engine is not enabled at the secret path, as shown by the first command vault secrets list, which lists the enabled secrets engines and their paths. The only enabled secrets engine is the transit secrets engine at the transit path. Therefore, the second command will fail with an error message saying that no secrets engine is mounted at the path secret/. To make the second command succeed, the kv secrets engine must be enabled at the secret path or another path, using the vault secrets enable command. For example, vault secrets enable -path=secret kv would enable the kv secrets engine at the secret path.Reference:kv - Command | Vault | HashiCorp Developer,vault secrets enable - Command | Vault | HashiCorp Developer
Limited Time Offer
25%
Off
Kenny
9 months agoLon
9 months agoWillard
9 months agoRikki
10 months agoLarae
10 months agoFlorinda
10 months agoAmira
10 months agoBenedict
10 months agoMabelle
10 months agoXuan
10 months agoEarleen
10 months agoCecil
10 months agoWilson
10 months agoJenelle
10 months ago