Comment 16 for bug 1224828

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?