While we don't store the outputs in the stack record, the previous approach did a force reload of the entire stack object every time we polled for state, which I think has the side-effect of re-resolving the outputs every time. So it'd be interesting to put in an explicit self.resolve_static_data(self.t[self.t.OUTPUTS]) somewhere like we'd previously have been doing via the Stack constructor?
Possibly related to the comment from Zane - in https:/ /github. com/openstack/ heat/commit/ 095a5eae434417e d8ba7bb3d73aacf 493ac51387 we made a change that means the parent Stack object is only partially refreshed while we're polling for state.
While we don't store the outputs in the stack record, the previous approach did a force reload of the entire stack object every time we polled for state, which I think has the side-effect of re-resolving the outputs every time. So it'd be interesting to put in an explicit self.resolve_ static_ data(self. t[self. t.OUTPUTS] ) somewhere like we'd previously have been doing via the Stack constructor?