validate-template fails to identify AWS::CloudFormation::Stack Properties TemplateBody as invalid about aws-cli HOT 4 OPEN

If it's only valid in some undocumented context : Then the issue is with the documentation.

If the documentation does not declare the unknown context then how can the tooling/users know what the context they must use is?

Considering Cfn is an AWS product, it has far too many bugs like this.

from aws-cli.

I think this is more about missing functionality than the Linter being wrong.

TemplateBody is a documented parameter:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cloudformation-stack.html#cfn-cloudformation-stack-templatebody

Do we need to raise a feature request to get a documented feature to work??? I just wasted a couple of hours trying to make this work, assuming I'd got something else wrong. "It must be right, it's in the docs. Maybe I've got my !Sub wrong or something..."

from aws-cli.

There's further context in aws-cloudformation/cfn-lint#2975

Apparently TemplateBody is only valid in... some unknown context, and it's not valid when using CFN to define a Stack.

from aws-cli.

Got the same issue. I want to deploy a cloudformation template using the CLI which creates two sub-stacks. I want to pass the template bodies to both stacks as variables (I extract the *.yaml-files' content and convert it into *.json-syntax) but I get the following error:

"Encountered unsupported property TemplateBody"

Just wasted some hours on trying to get this right. Now I have to change to S3 buckets using the TemplateURL property. Kind of annoying because its clearly part of the documentation.

from aws-cli.