You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 17, 2024. It is now read-only.
I used goformation.ParseYAML() to parse a working CloudFormation template that has some Lambda resources. The parse files with the following error:
json: cannot unmarshal number into Go struct field Template.Resources of type string
In general, the parser seems to be more sensitive to the YAML types that the real CloudFormation service is, which I guess is reasonable. However, I tracked this down to a parsing issue in AWSLambdaFunction_Environment. AWSLambdaFunction_Environment defines Variables as map[string]string, but the CloudFormation docs imply that any type is allowed as a value, https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-lambda-function-environment.html
So the JSON parsing that is done via goformation.ParseYAML() requires me to convert the value of data_volume_size to a string, but there doesn't seem to be a way to do that.
The text was updated successfully, but these errors were encountered:
I used
goformation.ParseYAML()
to parse a working CloudFormation template that has some Lambda resources. The parse files with the following error:In general, the parser seems to be more sensitive to the YAML types that the real CloudFormation service is, which I guess is reasonable. However, I tracked this down to a parsing issue in
AWSLambdaFunction_Environment
.AWSLambdaFunction_Environment
defines Variables asmap[string]string
, but the CloudFormation docs imply that any type is allowed as a value, https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-lambda-function-environment.htmlIn my case, I have something like this:
So the JSON parsing that is done via
goformation.ParseYAML()
requires me to convert the value ofdata_volume_size
to a string, but there doesn't seem to be a way to do that.The text was updated successfully, but these errors were encountered: