Steven Hardy c1868d2f56 Allow referencing rendered yaml files in resource_registry ... For backwards compatibility we need a fallback when an environment file references a file that's *.j2.yaml in the user --templates dir but it's rendered via the plan generation and is then downloaded to the local temporary tree. In this case we've got to rewrite the paths in the resource_registry values to point to the new tree where the rendered templates exist. Without this logic, some environment files (such as those enabling swap for all roles) no longer work, so it's a backwards compatibility workaround. Change-Id: I560784dc49842113563f617b343702bb045fca76 Closes-Bug: #1625783 (cherry picked from commit 4abd0cd791)		2016-10-12 07:50:09 +00:00
..
tests	Download templates from swift before processing with heatclient	2016-10-07 13:03:50 -04:00
v1	Allow referencing rendered yaml files in resource_registry	2016-10-12 07:50:09 +00:00
workflows	Add optional overcloud deploy roles_data.yaml override	2016-10-05 10:59:16 +00:00
__init__.py	Rename rdomanager_oscplugin to tripleoclient	2015-09-08 10:22:22 -04:00
constants.py	Add optional overcloud deploy roles_data.yaml override	2016-10-05 10:59:16 +00:00
exceptions.py	Stop plan creation when container exists	2016-09-26 07:58:48 +00:00
plugin.py	Display error message when socket is closed	2016-09-22 10:13:08 +00:00
utils.py	Deprecate a number of CLI args that map directly to Heat params	2016-09-28 22:13:58 +00:00