Nested Stacks cannot read their resource metadata
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Fix Released
|
High
|
Steven Hardy |
Bug Description
Raising this bug related to the issue described in https:/
Summary of way forward as proposed by Zane:
1) AWS::CloudForma
2) Other nested stacks don't show up in ListStacks &c. (i.e. we continue passing the parent stack as the "owner"), but can still be accessed normally by anyone who knows the ARN (which can be found from the PhysicalResourceId, and of course appears in e.g. WaitConditionHandle URLs of resources inside the nested stack).
Fixing this will solve one of the issues mentioned in https:/
Changed in heat: | |
status: | New → In Progress |
importance: | Undecided → High |
assignee: | nobody → Steven Hardy (shardy) |
milestone: | none → grizzly-rc1 |
Changed in heat: | |
status: | Fix Committed → Fix Released |
Changed in heat: | |
milestone: | grizzly-rc1 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/22998
Review: https:/