-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TaskDefinition.Options generated without field #297
Comments
I wonder this is an issue with the schema, as "AWS::ECS::TaskDefinition.Options" is declared with "Options": {
"additionalProperties": true,
"patternProperties": {
"^[a-zA-Z0-9]+$": {
"type": "string"
}
},
"type": "object"
} |
Looking at cloudformation schema https://d1uauaxba7bl26.cloudfront.net/latest/gzip/CloudFormationResourceSpecification.json I can't find the definition for the |
Where did you get this link from? When I dig into the link https://d1uauaxba7bl26.cloudfront.net/ it looks like the most recent version is from 2017, if the XML "" tag is correct. I do see the change made to the Docs though that supports this claim awsdocs/aws-cloudformation-user-guide@cb59b66. I tested a fargate stack, and the "AWS::ECS::TaskDefinition.Options" still works when included in the cloudformation template so I'm unsure but will ask internally to try to figure more out. |
This is the one used by |
Ok, cool makes sense |
The CloudFormation schema has the following, which looks correct to me at first glance. It should be generating a
|
It looks like this was actually corrected last night in the upstream CloudFormation specification, and the goformation code is generating properly now. Unfortunately there is another CloudFormation schema issue introduced that is causing our tests to fail and blocking a release. See issue #300. I have raised this internally. |
Fixed in #320 |
after code has been regenerated on #296
TaskDefinition_LogConfiguration.Options, which was previously a
map[string]string
, now is implemented as a*TaskDefinition_Options
, but the latter has no field that can be used to pass optionsThe text was updated successfully, but these errors were encountered: