Closed dave-moser closed 10 months ago
Might it have something to do with SAM CLI upgrading to v2.5 of cookiecutter? I see a reference to Implement new style for nested templates config in the release notes for cookiecutter 2.5.0. Both of these SAM aws-samples use multiple templates for the user to choose from.
I determined this is due to a new way cookiecutter configures multiple templates in one repo as of v 2.2. Additnal changes were implemented in v2.5. SAM CLI 1.103.0 updates cookie cutter to v2.5. Once I reorganized my repo to the new template folder structure, it works. I suspect this will affect anyone who published a SAM Template Project prior to Juky 2023 when the new formats were introduced.
Comments on closed issues are hard for our team to see. If you need more assistance, please either tag a team member or open a new issue that references this one. If you wish to keep having a conversation with other community members under this issue feel free to do so.
Description:
Performing a sam init against a custom template location that has multiple project templates results in a cookiecutter error. This only started happening with a recent update to the sam cli. It did not occur in v 1.95.0. I only started seeing it in 1.103.0.
You can see the error by attempting to init either of these 2 projects in aws-samples
Steps to reproduce:
Update your SAM CLI to the latest version (1.103)
Initialize a new project with either of these templates
Observed result:
You get a cookiecutter error
Expected result:
In prior versions of the CLI (at least 1.95.0) the project generated the folder structure without error. I'm not sure which CLI version this error started occuring. It is happening in 1.103.0
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.103.0Add --debug flag to command you are running