My initial reaction is that sounds good, but how is it different then params, or maybe a hidden param? Maybe they are conditionally assigned? Conditional params would be awesome too though. If param 1 is not set, then param 2 is required...
Thanks, Kevin ________________________________ From: Thomas Herve Sent: Thursday, March 31, 2016 1:40:33 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [openstack-dev] [Heat] Re-evaluate conditions specification Hi all, As the patches for conditions support are incoming, I've found something in the code (and the spec) I'm not really happy with. We're creating a new top-level section in the template called "conditions" which holds names that can be reused for conditionally creating resource. While it's fine and maps to what AWS does, I think it's a bit short-sighted and limited. What I have suggested in the past is to have a "variables" (or whatever you want to call it) section, where one can declare names and values. Then we can add an intrinsic function to retrieve data from there, and use that for examples for conditions. It solves that particular issue, and it opens some interesting possibilities for reducing duplication in the template, as we could build arbitrary values out of parameters or attributes that can then be reused several times. Thoughts? -- Thomas __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
