Make heat-translator available via python-openstackclient

Registered by Sahdev Zala

We had a consensus at the Atlanta Juno Summit that the original design idea of making heat-translator available via python-heatclient is a good way to integrate tool into Heat initially. Once the tool is stable and mature, it can be moved to the heat server side.

This requires more discussion on what's the best possible way to make it happen.

As per the latest discussion at the Vancouver summit, since the python-openstackclient is available to use (which is created as an unified openstack client and comes with pre-built support for some main programs like keystone) and possibly all clients, including python-heatclient, will move to use it with a required plug-in it makes sense to make heat-translator available via python-openstackclient.

Blueprint information

Status:
Complete
Approver:
None
Priority:
High
Drafter:
Sahdev Zala
Direction:
Needs approval
Assignee:
Sahdev Zala
Definition:
New
Series goal:
None
Implementation:
Implemented
Milestone target:
None
Started by
Sahdev Zala
Completed by
Sahdev Zala

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:osc,n,z

Addressed by: https://review.openstack.org/191898
    Create an OSC plugin for heat-translator

Gerrit topic: https://review.openstack.org/#q,topic:add_output_file,n,z

Addressed by: https://review.openstack.org/191936
    Add the ability to set output file

Gerrit topic: https://review.openstack.org/#q,topic:params,n,z

Addressed by: https://review.openstack.org/191943
    Add support for parameters to translate template

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.