I have a problem `Pulumi dev yaml` contains a variable `debu

Question

I have a problem `Pulumi dev yaml` contains a variable `debug true` I pass this to ECS Task container definition and get an error ```Error decoding JSON json cannot unmarshal bool into Go struct field KeyValuePair Environment Value of type string Examine values at TaskDefinition ContainerDefinitions ``` This is the code ```import json import pulumi def json output element gt pulumi Output Dump python object to JSON string as pulumi Output return pulumi Output from input element apply json dumps container definition = name self config container name image self config image name portMappings containerPort self config application port protocol tcp environment name k value v for k v in self config env vars items linuxParameters initProcessEnabled True logConfiguration logDriver awslogs options awslogs group self config log group name awslogs region self config aws classic provider region awslogs stream prefix self config log stream prefix or ecs self task definition = classic ecs TaskDefinition f self config name td args=classic ecs TaskDefinitionArgs family=f self config name cpu=self config task cpu memory=self config task memory network mode= awsvpc requires compatibilities= FARGATE execution role arn=self task exec role arn task role arn=self task role arn container definitions=json output container definition tags=self config tags ```

prehistoric-activity-61023 · Answer

based on the error message how does the content of `self config env vars` look like

prehistoric-activity-61023 · Answer

I think it might expect values as strings and it fails because at least of the values is boolean

prehistoric-activity-61023 · Answer

I d try to convert all values to strings first ``` name k value str v for k v in self config env vars items ```

prehistoric-activity-61023 · Answer

considering that all values `v` can be easily converted using `str v `

prehistoric-activity-61023 · Answer

Ok you wrote that you have variable `debug true` I assume that `environment` in container definition stands for environment variables then it makes sense that they are parsed later as strings If so you have to properly convert this boolean value to string gt that depends on how your application handles it Just remember if you use `str v ` you re gonna get upper case versions ``` gt gt gt str True True gt gt gt str False False ``` If you want to fully control the conversion process simply write a helper function that suits your needs ```def convert to env string v Any gt str if isinstance v str return v if isinstance v bool return true if v else false raise ValueError unsupported type ``` and use it later when creating map for environment field ``` name k value convert to env string v for k v in self config env vars items ```

great-sunset-355 · Answer

Yeah it assumes all values to be a string

great-sunset-355 · Answer

and I wanted to avoid the conversion function I ll keep it as is knowing the limitation and have high hopes for aws native

prehistoric-activity-61023 · Answer

do you think it s a limitation and aws native will resolve this

prehistoric-activity-61023 · Answer

I wouldn t say so In most cases environment variables are treated as strings same goes for k8s deployments or reading envs using `os environ` in python cause you cannot relay type information using them

great-sunset-355 · Answer

That s difficult to say since I did not try this use case exactly but I noticed that in python `inputs` that required `JSON string` now accept python `Dictonary` hence the assumptions

prehistoric-activity-61023 · Answer

Ok this part might change Right now `container definitions` are supposed to be JSON strings and they actually could be python `dicts` However your issue was related to the type of `environment` field within that dictionary and I guess this part won t change slightly smiling face