Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
cli command to transform sam template to regular cloudformation template?
See original GitHub issueDescribe your idea/feature/enhancement
I believe it could be useful to add a command to allow a user to see the cloudformation template produced after serverless transforms are applied.
Proposal
sam transform --template-file PATH --output-template-file PATH
Additional Details
A couple reasons I see value here:
-
education - for a new user, there’s mystery around the effects of using sam syntax … e.g. what policies are going to be automatically generated based on various properties i specify
-
some mechanisms in the wild are not yet friendly towards serverless transforms and being able to provide them with vanilla cloudformation, while still taking advantage of sam syntax during compose phase is a nice compromise
Issue Analytics
- State:
- Created 4 years ago
- Reactions:17
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Another upvote. I would want to use the SAM CLI to generate the CF template to be then aggregated as a child template in a parent application stack.
Our group could also use this. Developers do a SAM build for local testing, but cloud engineers maintain a separate Cloud Formation template for deployment. Generating the CF template would reduce work and errors.