AWS CFT enforces that you define all the parameters that all run times might need up front. Ex:
var_x_1: 123
var_x_2: 456
var_x_3: 789
var_y_1: abc
var_y_2: def
var_y_3: ghi
Proposing to allow parametrizing vars to something like this:
var_x: {{x}}
var_y: {{y}}
Then in PCF CFT Particle's config dict/json, define the the k:v like this:
"cft_vars": ["x": "123", "y":"def"]
AWS CFT enforces that you define all the parameters that all run times might need up front. Ex: var_x_1: 123 var_x_2: 456 var_x_3: 789 var_y_1: abc var_y_2: def var_y_3: ghi
Proposing to allow parametrizing vars to something like this: var_x: {{x}} var_y: {{y}}
Then in PCF CFT Particle's config dict/json, define the the k:v like this: "cft_vars": ["x": "123", "y":"def"]
Similar logic was used in EC2 Instance particle for usedata_template https://github.com/capitalone/Particle-Cloud-Framework/blob/master/pcf/particle/aws/ec2/ec2_instance.py#L118