Keeton Hodgson

@copumpkin like @chrisoverzero said, you can remove the stage `Stage` by specifying anything in the `OpenApiVersion` property, and this was to maintain backwards compatibility. We definitely can make this more...

That is a valid SAM template and deploys via CloudFormation. It appears that SAM is trying to resolve the parameter passed into AutoPublishAlias and can't, thus throwing an error. Allowing...

Talked with @jfuss who brought up that template validation should depend on whether or not a template is valid, not on the existence of a parameter. Customers should not have...

Still seeing this issue, it has not been resolved yet.

Just ran this issue again. Results: `sam validate` failed with `Error: [InvalidResourceException('SkillFunction', "'AutoPublishAlias' must be a string or a Ref to a template parameter")] ('SkillFunction', "'AutoPublishAlias' must be a string...

#1162 is another case that this would fix.

Similar to #1305 for environment variables. This would be good to support, look at #1305 at how to implement this change.

@beck3905 I like this idea. Like you posted, there are several features in https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-apigateway-method.html that could be useful in API Events. Some of these issues are: * Authorization Scopes (#652)...

@praneetap mentioned this in https://github.com/awslabs/serverless-application-model/issues/931#issuecomment-534463087 This is an open feature request to add validators.

@tuler agree, it looks like SAM should add an error at that point for an incorrect configuration. It looks like SAM reads it as a list, some digging is needed...