mirror of
				https://github.com/optim-enterprises-bv/vault.git
				synced 2025-11-03 20:17:59 +00:00 
			
		
		
		
	@mitchellh suggested we fork `cli` and switch to that. Since we primarily use the interfaces in `cli`, and the new fork has not changed those, this is (mostly) a drop-in replacement. A small fix will be necessary for Vault Enterprise, I believe.
		
			
				
	
	
		
			62 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
			
		
		
	
	
			62 lines
		
	
	
		
			1.4 KiB
		
	
	
	
		
			Go
		
	
	
	
	
	
// Copyright (c) HashiCorp, Inc.
 | 
						|
// SPDX-License-Identifier: BUSL-1.1
 | 
						|
 | 
						|
package command
 | 
						|
 | 
						|
import (
 | 
						|
	"strings"
 | 
						|
 | 
						|
	"github.com/hashicorp/cli"
 | 
						|
)
 | 
						|
 | 
						|
var _ cli.Command = (*KVCommand)(nil)
 | 
						|
 | 
						|
type KVCommand struct {
 | 
						|
	*BaseCommand
 | 
						|
}
 | 
						|
 | 
						|
func (c *KVCommand) Synopsis() string {
 | 
						|
	return "Interact with Vault's Key-Value storage"
 | 
						|
}
 | 
						|
 | 
						|
func (c *KVCommand) Help() string {
 | 
						|
	helpText := `
 | 
						|
Usage: vault kv <subcommand> [options] [args]
 | 
						|
 | 
						|
  This command has subcommands for interacting with Vault's key-value
 | 
						|
  store. Here are some simple examples, and more detailed examples are
 | 
						|
  available in the subcommands or the documentation.
 | 
						|
 | 
						|
  Create or update the key named "foo" in the "secret" mount with the value
 | 
						|
  "bar=baz":
 | 
						|
 | 
						|
      $ vault kv put -mount=secret foo bar=baz
 | 
						|
 | 
						|
  Read this value back:
 | 
						|
 | 
						|
      $ vault kv get -mount=secret foo
 | 
						|
 | 
						|
  Get metadata for the key:
 | 
						|
 | 
						|
      $ vault kv metadata get -mount=secret foo
 | 
						|
	  
 | 
						|
  Get a specific version of the key:
 | 
						|
 | 
						|
      $ vault kv get -mount=secret -version=1 foo
 | 
						|
 | 
						|
  The deprecated path-like syntax can also be used, but this should be avoided 
 | 
						|
  for KV v2, as the fact that it is not actually the full API path to 
 | 
						|
  the secret (secret/data/foo) can cause confusion:   
 | 
						|
  
 | 
						|
      $ vault kv get secret/foo
 | 
						|
 | 
						|
  Please see the individual subcommand help for detailed usage information.
 | 
						|
`
 | 
						|
 | 
						|
	return strings.TrimSpace(helpText)
 | 
						|
}
 | 
						|
 | 
						|
func (c *KVCommand) Run(args []string) int {
 | 
						|
	return cli.RunResultHelp
 | 
						|
}
 |