Skip to content
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

SAM Templates cannot be deployed by CloudFormation Stack Sets #15

Open
tomwwright opened this issue Oct 9, 2020 · 1 comment
Open
Labels
module/core type/debt Technical debt that needs to be addressed in the future

Comments

@tomwwright
Copy link
Owner

tomwwright commented Oct 9, 2020

CloudFormation Stack Sets cannot be used to deploy SAM templates because Stack Sets do not support CloudFormation Macro Transform definitions in templates

https://docs.amazonaws.cn/en_us/AWSCloudFormation/latest/UserGuide/template-macros.html

The solution here is to "pre-transform" the template with the SAM library

https://pypi.org/project/aws-sam-translator/
https://github.com/aws/serverless-application-model/blob/develop/bin/sam-translate.py

Once rendered into a regular CloudFormation template it can be deployed in a Stack Set

This functionality is important to Little Orange as it intends to deploy lots of functionality via Stack Sets

@tomwwright tomwwright added type/feature Feature or functionality that is well-formed and can be implemented and closed module/core labels Oct 9, 2020
tomwwright added a commit that referenced this issue Oct 11, 2020
…ver, implement transforming to vanilla CloudFormation
@tomwwright
Copy link
Owner Author

BuildSAM module has support for a ApplySAMTranslate property to "pre-transform" the SAM template into vanilla CloudFormation suitable for use with Stack Sets

Note that due to #16 this functionality is only specifically useful -- for cases where a Stack Set needs to be deployed across many accounts but not many regions

@tomwwright tomwwright added type/debt Technical debt that needs to be addressed in the future and removed type/feature Feature or functionality that is well-formed and can be implemented and closed labels Oct 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
module/core type/debt Technical debt that needs to be addressed in the future
Projects
None yet
Development

No branches or pull requests

1 participant