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 list /identity/group/{id,name} returns 404 if no groups exist #5861

Closed
yajo opened this issue Nov 28, 2018 · 2 comments
Closed

vault list /identity/group/{id,name} returns 404 if no groups exist #5861

yajo opened this issue Nov 28, 2018 · 2 comments
Milestone

Comments

@yajo
Copy link

yajo commented Nov 28, 2018

Describe the bug
If no groups exist, instead of returning an empty list, the API returns a 404 error.

To Reproduce
Steps to reproduce the behavior:

  1. Run vault list /identity/group/id or vault list /identity/group/name when no groups exist.

Expected behavior
It should return 200 with an empty list.

Environment:

  • Vault Server Version (retrieve with vault status): 0.11.5
  • Vault CLI Version (retrieve with vault version): Vault v0.11.5 ('a59ffa4a0f09bbf198241fe6793a96722789b639')
  • Server Operating System/Architecture: Docker image.

Vault server configuration file(s):

  backend:
    file:
      path: /vault/file
  ui: true

Additional context:
The docs say 404 is not an expected return:

@ncabatoff
Copy link
Collaborator

This appears to be a documentation bug, based on #1365.

@chrishoffman chrishoffman modified the milestones: 1.0.2, 1.0.3 Jan 3, 2019
@jefferai
Copy link
Member

jefferai commented Feb 1, 2019

We're thinking over lists and whether they generally be 404 or 204. I'm closing this since we're thinking about it for more than just this specific instance.

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

4 participants