Closed beck3905 closed 5 years ago
Currently pinned to version 1.11.0, will update to the latest in next release.
Being this far behind is causing me problems. I install both aws-sam-cli
and cfn-lint
as dev dependencies on a per-project basis using pipenv
. cfn-lint
now depends on the SAM translator being at least 1.13, and since aws-sam-cli
pins the version at 1.11, there's an unresolvable conflict. Here's a Pipfile
demonstrating the problem. Does the SAM CLI really need to pin the version? I could install it with pipx
, I guess, but I prefer to have my Python tools localized to my projects.
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"
[dev-packages]
aws-sam-cli = "*"
cfn-lint = "*"
[requires]
python_version = "3.6"
During the 0.21.0 release, we ran into an issue with one of our installers and the upgraded aws-sam-translator
. Since then, we have addressed the issue and are staging this for a release (#1412 was the upgrade PR).
Description
aws-sam-cli lists aws-sam-translator==1.10.0 in the requirements/base.txt however the latest version of aws-sam-translator is 1.13.1. There are new features available in the latest version of aws-sam-translator that fail to build using the latest version of aws-sam-cli.
For example, I have an AWS::Serverless::API resource in my template and I am trying to use the GatewayResponses property. When running SAM build I get an error during template validation.
This is a different symptom/reasoning than issue https://github.com/awslabs/aws-sam-cli/issues/1266
Steps to reproduce
Observed result
Expected result
Successful build of my sam template.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 0.19.0Add --debug flag to command you are running