Open Stack

On Tue, Jun 18, 2013 at 11:01 PM, Adrian Otto <adrian.otto at rackspace.com>wrote:

> On Jun 18, 2013, at 6:09 PM, Angus Salkeld <asalkeld at redhat.com> wrote:
> > To me one of the most powerful and apealing things of Heat is the
> > ability to reproducibly re-create a stack from a template. This
> > new public API is going to make this difficult.
>
> Adding an API only makes it difficult if you decide to bypass templates
> and use the API. You can still be disciplined and keep your templates
> updated to achieve the reproducible goal. Yes, and API of this sort is a
> sharp instrument, but it can be useful if applied properly.
>

It seems we could trivialize the task of keeping your template up to date
by providing an API for fetching a template that reflects the current
stack. Does that sound sensible given the current direction of the design
of Heat?

-- 
IRC: radix
Christopher Armstrong
Rackspace
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20130618/e97cef4d/attachment.html>