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

Add support for querying OV services by resource and status #49

Open
danielreed opened this issue Feb 15, 2017 · 0 comments
Open

Add support for querying OV services by resource and status #49

danielreed opened this issue Feb 15, 2017 · 0 comments

Comments

@danielreed
Copy link
Member

danielreed commented Feb 15, 2017

Add support to query the OneView index service by resource and status:

A new listener should respond to something like ‘show all critical hardware’ or ‘show all profiles in warning status’.

Will need new index class in the SDK (needs support for query parameters) and a new listener.

Example query may look like this:

/rest/index/resources?sort=name:asc&count=100&start=0&category=server-hardware&query="status:'Warning'"

@danielreed danielreed added this to the v1-release milestone Apr 19, 2017
@kelseycribari kelseycribari self-assigned this Jun 15, 2017
kelseycribari pushed a commit to kelseycribari/hpe-oneview-hubot that referenced this issue Jun 19, 2017
jonmccormick pushed a commit that referenced this issue Jun 19, 2017
* Issue #49 - support for querying by resource and status

* Patch 1 -- fix mistake with mixing up classes

* Patch 2 -- remove unneccessary params from lexer

* Patch 3 -- remove console log statements

* Patch 4 -- refactored to make one function for cleaner code
@kelseycribari kelseycribari reopened this Jun 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants