-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Failed to publish to SAR with Error: ResultPath being null #1618
Comments
@alexcasalboni From the error is seems like your template is invalid. SAR supports Can you provide the template (redacted parts if you need to)? It seems like a SAR issue or that your template is not valid. |
@jfuss you can find the whole template here: https://github.com/alexcasalboni/aws-lambda-power-tuning/blob/917d021ce5188e75dee7e4bee0452122ce141769/template.yml The error I get from SAR is about |
I was just trying to deploy a stack with the same |
Found that the cfn-lint folks are tracking the linter issue, in case they are related. |
This is still a problem with CloudFormation YAML templates in the state machine. It's 2022 and this problem has been around for 2 years. When can we expect a fix? |
The CloudFormation service doesn't support the serverless transform should be converting this to a string (property) which makes the template valid for CloudFormation because the null is now in a string. You can look into cfn-lint issue above for more details on that conversion. |
Hello! I tried to reproduce this issue and I can publish to SAR with
Close this issue for now and feel free to reopen if you have other questions |
Description: If you deploy a
AWS::Serverless::StateMachine
with the AWS SAM CLI it works great, but you cannot publish this app/stack to SAR.Steps to reproduce the issue:
AWS::Serverless::StateMachine
in itsam package
andsam publish
Observed result:
App publication fails with this error:
Expected result:
I'd expect to app to be published successfully, or at least I'd expect SAM CLI to provide a meaningful error.
The text was updated successfully, but these errors were encountered: