Skip to content
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

Documentation output doesn't match real output #2116

Closed
ThisIsMissEm opened this issue Nov 21, 2016 · 3 comments
Closed

Documentation output doesn't match real output #2116

ThisIsMissEm opened this issue Nov 21, 2016 · 3 comments

Comments

@ThisIsMissEm
Copy link

Hi! I just started playing with Vault, it looks great. Reading the documentation, I was a little confused when looking at the output of vault read as what in the documentation is different to the output I get (using latest 64bit binary from the downloads page)

What I get:

$ vault read secret/hello                                                                                                                                      
Key             	Value
---             	-----
refresh_interval	768h0m0s
excited         	yes
value           	world

$ vault read -format json secret/hello                                                                                                                         
{
	"request_id": "68315073-6658-e3ff-2da7-67939fb91bbd",
	"lease_id": "",
	"lease_duration": 2764800,
	"renewable": false,
	"data": {
		"excited": "yes",
		"value": "world"
	},
	"warnings": null
}

Expected:

$ vault read secret/hello
Key             Value
lease_duration  2764800
excited         yes
value           world

$ vault read -format=json secret/hello
{
  "lease_id": "",
  "lease_duration": 0,
  "renewable": false,
  "data": {
    "excited": "yes",
    "value": "world"
  }
}

I'm guessing the case here is just that the documentation is slightly out of date; If that is the case, and you'd like a PR to update it, just let me know and I'd be happy to send in PRs.

@jefferai
Copy link
Member

It's just out of date documentation...a PR would be great!

@ThisIsMissEm
Copy link
Author

Okay, I'll do one up!

ThisIsMissEm pushed a commit to ThisIsMissEm/vault that referenced this issue Nov 21, 2016
These were discovered to be out of date as per hashicorp#2116
@ThisIsMissEm
Copy link
Author

Have created #2117

jefferai pushed a commit that referenced this issue Nov 22, 2016
These were discovered to be out of date as per #2116
jefferai pushed a commit that referenced this issue Nov 22, 2016
These were discovered to be out of date as per #2116
chrishoffman added a commit to chrishoffman/vault that referenced this issue Nov 24, 2016
* upstream/master:
  Add version sha to server startup output
  Change current version number
  changelog++
  Don't say mlock is supported on OSX when it isn't. (hashicorp#2120)
  Change command examples for First Secrets hashicorp#2116 (hashicorp#2117)
  changelog++
  cli: fix bug with 'vault read -field=...' when the field value contains a printf formatting verb (hashicorp#2109)
  Update docs to fix hashicorp#2102
  Updating changelog
  http: increase request limit from 8MB to 32MB
  http: limit maximum request size
  Update libraries doc for Haskell community library (hashicorp#2101)
  Don't exclude 0 from the set of valid polynomials in Shamir. This leads to a potential (although extremely trivial) amount of information leakage.
  Bump proto files after update
  changelog++
  check for failure on that mysql query (hashicorp#2105)
  Bump deps
  Document bug causing certain LDAP settings to be forgotten on upgrade to 0.6.1+.
  Set number of pester retries to zero by default and make seal command… (hashicorp#2093)
michael-k pushed a commit to michael-k/vault that referenced this issue Mar 5, 2017
vishalnayak pushed a commit that referenced this issue Mar 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants