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

Vault Status Command Differs Depending on Format #9185

Closed
jamiegwatkin opened this issue Jun 10, 2020 · 3 comments
Closed

Vault Status Command Differs Depending on Format #9185

jamiegwatkin opened this issue Jun 10, 2020 · 3 comments
Labels
bug Used to indicate a potential bug core/cli

Comments

@jamiegwatkin
Copy link

Describe the bug
The output of vault status differs depending on the format selected.

For instance, vault status -format=table has the following HA output:

HA Enabled               true
HA Cluster               https://10.10.99.20:8201
HA Mode                  active

However those three keys are missing form vault status -format=json.

To Reproduce
Steps to reproduce the behavior:

  1. Execute vault status -format=json
  2. Execute vault status -format=table
  3. Notice how the key and value pairs are not the same

Expected behavior
I expect to be able to get the same information when I execute vault status -format=json as when I execute vault status -format=table.

Environment:

  • Vault Server Version (retrieve with vault status): 1.4.2
  • Vault CLI Version (retrieve with vault version): Vault v1.4.2
  • Server Operating System/Architecture:
ubuntu@ip-10-10-75-128:~$ cat /etc/*version*
buster/sid
Ubuntu 18.04.4 LTS (Bionic Beaver)`
@dedamico
Copy link
Contributor

This appears to be same/similar to #6179

@akshya96
Copy link
Contributor

akshya96 commented Mar 1, 2023

Hi @jamiegwatkin, We only display the relevant fields for "table" format. I've added the expected differences in the vault status documentation #19361.

@akshya96
Copy link
Contributor

akshya96 commented Mar 2, 2023

Since the expected differences are documented, I'm going to go ahead and close this issue now. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Used to indicate a potential bug core/cli
Projects
None yet
Development

No branches or pull requests

4 participants