heatclient should accept multiple environment files
Bug #1350403 reported by
Peter Belanyi
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-heatclient |
Fix Released
|
High
|
Peter Belanyi |
Bug Description
Currently heatclient accepts only one environment file, while it would be useful to accept more than one (in tripleo we would like to pass in several enviroment files, e.g. 1 containing parameters, 1 for resource mapping).
heatclient loads the env file and passes its contents to the api as a dictionary, so it seems possible to process several files, merge the resulting dicts and send it to the api.
Changed in heat: | |
assignee: | nobody → Peter Belanyi (pbelanyi) |
Changed in heat: | |
status: | New → In Progress |
Changed in python-heatclient: | |
importance: | Undecided → High |
Changed in python-heatclient: | |
milestone: | none → v0.2.11 |
Changed in python-heatclient: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
To clarify, this is about adding some convenience preprocessing to python-heatclient, not modifying the heat API right?
If so, then this should be marked as affecting python-heatclient not heat.
Also, can you outline how you expect to handle the merge strategy, in the event of collisions between the environment files to be merged?