First time here? Check out the FAQ!
2016-09-06 21:19:14 -0600 | received badge | ● Famous Question (source) |
2016-07-30 15:40:56 -0600 | received badge | ● Scholar (source) |
2016-07-30 15:40:55 -0600 | commented answer | Parameter input in nested heat templates I thought this might be the case. Oh well, perhaps in a future version it will be able to pull in parameters from child templates. Thanks for taking the time to answer! |
2016-07-30 15:40:53 -0600 | received badge | ● Supporter (source) |
2016-07-28 11:48:17 -0600 | received badge | ● Notable Question (source) |
2016-07-26 08:00:35 -0600 | received badge | ● Popular Question (source) |
2016-07-15 14:56:59 -0600 | asked a question | Parameter input in nested heat templates I am currently in the process of building out nested heat templates where the master template defines some globally-applicable parameters and then just calls other templates as resources as required: etc. My resource templates look like this: As it stands right now, if I call the master template in horizon, it won't ask for parameter input for parameters that exist only in the sub-templates (such as network_ID in the above example), only the ones that are explicitly defined in the master. I could just go and declare all parameters across all templates in the master, but that is inelegant and kind of defeats the purpose of the modularity I am trying to achieve. Is what I am asking for possible, or does this functionality not exist yet? |