Extra API calls will be needed to determine this, so it may not be appropriate to show this in a config-list or config-show command output.
This might be better done as a --config filter option on deployment-list, which would be more appropriately implemented as one of the new openstackclient commands: https://blueprints.launchpad.net/heat/+spec/heat-support-python-openstackclient http://specs.openstack.org/openstack/heat-specs/specs/mitaka/python-openstackclient.html https://etherpad.openstack.org/p/heat-support-python-openstackclient
We'd prefer to have a soft-freeze on UX based improvements to existing heat commands, so you might consider volunteering to implement the new 'openstack software config' and 'openstack software deployment' commands
Extra API calls will be needed to determine this, so it may not be appropriate to show this in a config-list or config-show command output.
This might be better done as a --config filter option on deployment-list, which would be more appropriately implemented as one of the new openstackclient commands: /blueprints. launchpad. net/heat/ +spec/heat- support- python- openstackclient specs.openstack .org/openstack/ heat-specs/ specs/mitaka/ python- openstackclient .html /etherpad. openstack. org/p/heat- support- python- openstackclient
https:/
http://
https:/
We'd prefer to have a soft-freeze on UX based improvements to existing heat commands, so you might consider volunteering to implement the new 'openstack software config' and 'openstack software deployment' commands