tree 7ea537a991a9aeda60c9d43a14340fe567a29364
parent 47039e2bdea90b7424753f76d597936638c401e8
author Zane Bitter <zbitter@redhat.com> 1500500140 -0400
committer Zane Bitter <zbitter@redhat.com> 1500647434 -0400

Get dep_attrs from StackDefinition

Since function.dep_attrs() returns logical resource names (rather
than actual objects), we can just as easily use the StackDefinition to
calculate it instead of the Stack and Resource objects.

In the legacy path, we must ensure we use the StackDefinition from the
*new* stack to determine which attributes to include in the NodeData, since
that's what we're going to be using it for. In the convergence path the
current stack definition already contains the new template.

Also, update the *new* stack's definition with the NodeData obtained from
completed resources (in addition to the existing stack's), so that that
data may be used in calculating the dep_attrs for future resources. This is
required when get_attr functions are nested in the template.

Change-Id: I23efcc091eae53470f7f9cb3ca21e09f00f43808
Partially-Implements: blueprint stack-definition