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

Remove resource name from LIST API response #46

Closed
NajmudheenCT opened this issue May 21, 2020 · 3 comments
Closed

Remove resource name from LIST API response #46

NajmudheenCT opened this issue May 21, 2020 · 3 comments
Assignees
Labels
bug Something isn't working High Priority High Priority Label
Milestone

Comments

@NajmudheenCT
Copy link
Member

Issue/Feature Description:
Currently the LIST API reposnse ( v/storages, v1/pools) contain resource name as key in the response . Need to remove this as to comply with API spec
v1_pools

Why this issue to fixed / feature is needed(give scenarios or use cases):
Not in align with API spec
How to reproduce, in case of a bug:
GET /v1/pools Query
Other Notes / Environment Information: (Please give the env information, log link or any useful information for this issue)

@NajmudheenCT NajmudheenCT self-assigned this May 21, 2020
@NajmudheenCT NajmudheenCT added bug Something isn't working High Priority High Priority Label labels May 21, 2020
@NajmudheenCT NajmudheenCT added this to the May2020 milestone May 21, 2020
@ghost ghost deleted a comment from skdwriting May 25, 2020
@ghost
Copy link

ghost commented May 25, 2020

This issue was moved by skdwriting to sodafoundation/sim#87.

@ghost ghost closed this as completed May 25, 2020
@kumarashit
Copy link
Collaborator

/move sim

@ghost
Copy link

ghost commented May 25, 2020

⚠️ You must have write permission for the source repository.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working High Priority High Priority Label
Projects
None yet
Development

No branches or pull requests

2 participants