Comment 1 for bug 1767514

Revision history for this message
Zane Bitter (zaneb) wrote :

It occurs to me that we could potentially encounter the same issue at the next layer down with any provider resources contained in the scaled unit. I'm not sure what the answer to that is. Duplicating all of the files and rewriting the child templates/environments to map all of the right versions seems like it would get out of hand quite quickly.

Maybe we have to add a parameter to the stack-update RPC call to limit which resources can be updated? (As long as we only use it internally - i.e. for stuff that we know has no dependencies - it might not be too hard to exclude some resources from the graph.)