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

Unify the clients #35

Closed
pilhuhn opened this issue Mar 20, 2016 · 0 comments
Closed

Unify the clients #35

pilhuhn opened this issue Mar 20, 2016 · 0 comments
Assignees
Milestone

Comments

@pilhuhn
Copy link
Member

pilhuhn commented Mar 20, 2016

Currently we have inventoryclient, metricsclient, alertclient and so on, where the user needs to instantiate each client separately.

We need to have one hawkular-client that the gets the base path of hawkular and/or the metrics server and which then internally creates those client objects so that the user can do something like

client = Hawkular.client.new(creds:..., base_path:..., options:...) 
inv_client = client.inventory
inv_client.list_feeds
alert_client = client.alerts
alert_client.create_trigger 

and so on.

@pilhuhn pilhuhn added this to the 0.3 milestone Mar 20, 2016
jkremser added a commit to jkremser/hawkular-client-ruby that referenced this issue Mar 22, 2016
… component clients, so that one could call everything from 1 place, this should also fix the issue hawkular#23
jkremser added a commit to jkremser/hawkular-client-ruby that referenced this issue Mar 22, 2016
… component clients, so that one could call everything from 1 place, this should also fix the issue hawkular#23
@jkremser jkremser self-assigned this Mar 24, 2016
jkremser added a commit that referenced this issue Mar 29, 2016
…nt clients, so that one could call everything from 1 place, this should also fix the issue #23

Using the term hawkular_client instead.
@pilhuhn pilhuhn closed this as completed Apr 6, 2016
jkremser added a commit to jkremser/hawkular-client-ruby that referenced this issue Apr 21, 2016
… component clients, so that one could call everything from 1 place, this should also fix the issue hawkular#23

Using the term hawkular_client instead.
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