Heatclient should be easier to use via python
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-heatclient |
Fix Released
|
Medium
|
Rabi Mishra |
Bug Description
Some/many other clients provide an easy way to create a Client object without direct interaction with keystone, e.g novaclient allows this:
from novaclient import client
nova = client.
http://
For heat it's more like this:
from heatclient import client as heatclient
from keystoneclient.v3 import client
c = client.
endpoint = c.service_
heat = heatclient.
It would be convenient if we allowed folks to pass the auth_url directly to the heatclient.Client constructor and did this work of getting the token/endpoint for them.
Relatedly I don't think it's possible to create a keystoneclient session object and reuse it with heatclient, so it'd be good to fix that too.
Changed in python-heatclient: | |
status: | New → Triaged |
importance: | Undecided → Medium |
Changed in python-heatclient: | |
status: | In Progress → Fix Released |
I think it's possible to use session with heatclient.
>>>heat = client. Client( VERSION, session=sess, service_ type='orchestra tion').
Though we can default the service_type, if not specified like other clients. I've pushed a patch to fix that.