Scenario:
1. Create 3-level stack from the command line (test-stack-adopt.sh in attached test-stack-adopt.zip does this and all subsequent steps).
2. Abandon stack.
3. Adopt stack in Python, also providing the "files" map for the nested templates.
4. Note the difference between providing the 2nd-level and 3rd-level templates in the map:
* 2nd-level: with the full "file://" path seen by the command-line client at stack creation time;
* 3rd-level: with the template name only, i.e. the way it is referenced inside the template.
Presumably (though not tested), if the stack is created in Python (instead of using the command line client), compiling the "files" map in-place, then the same map can be used for adopting the stack without the above problem.
Is this fix in python-heatclient is what you wanted?: https:/