Comment 17 for bug 1224828

Ton,
I really thought about adding just that extra column when trying to
implement cancel-update. In the end it looks like I managed to complete
without it, but IMO the implementation would be quite cleaner and more
straightforward.

Best,
Pavlo.

On Thu, Sep 4, 2014 at 1:25 AM, Ton Ngo <email address hidden> wrote:

> Agree, I am finishing up the patches to handle the parameters, then will
> add new patches for environment and templates.
> To reuse existing template, we will need to save a copy of the original
> template. As Zane pointed out, the current raw_template in the DB is not
> guaranteed to be the original template since it can be modified to reflect
> the real stack resources. Saving the original template would require a new
> column in the stack table and some code to manage it.
> Since this costs some resource and adds some complexity, I had posted this
> question earlier on the ML for feedback . Clint felt the user should
> manage their own templates outside of Heat.
> Does anyone else have feedback or suggestions?
> Could there be other use cases requiring the original template?
>
> --
> You received this bug notification because you are subscribed to heat.
> Matching subscriptions: heat bugs, heatclient
> https://bugs.launchpad.net/bugs/1224828
>
> Title:
> heat stack-update wants all parameters and the template all over again
>
> Status in Orchestration API (Heat):
> In Progress
> Status in Python client library for heat:
> In Progress
> Status in Tuskar:
> Triaged
>
> Bug description:
> If I'm changing one parameter in a stack - e.g. a service password
> definition, having to supply everything all over again is painful.
>
> It would be awesome to be able to go
> heat stack-update mycluster -P "AdminPassword=newvalue" and have that
> use the existing template in the live stack, and all the existing
> parameters just updating the value of the one parameter.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/heat/+bug/1224828/+subscriptions
>