You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developing large AWS SAM applications can lead to unwieldy and difficult-to-maintain template files. AFAIK Currently, there's no way to include other modules besides using nested stacks which doesn't quite seem to fulfill the purpose I'd like to use it for
As your infrastructure grows, common patterns can emerge in which you declare the same components in multiple templates. You can separate out these common components and create dedicated templates for them. Then use the resource in your template to reference other templates, creating nested stacks.
Similar discussions?
Possibly #2734 but their problem seem to be primarily about hitting CF resource count limit and using multiple templates as a solution.
Describe the persona of someone who is facing this problem?
Developers who work on large complex serverless applications have a hard time finding related component in large template files (1000+ lines). They seek a more granular and efficient way to split templates to enhance code readability.
How do developers work around this problem today?
They resort to nested stacks or create custom scripts to combine templates manually. These workarounds can be cumbersome and error-prone, adding unnecessary complexity to the development process.
Describe your proposed solution?
Introduce a new mechanism within AWS SAM to allow template splitting at a more granular level, such as by individual resources or functions. Here's a conceptual example:
How is the proposed feature better than the workaround?
This proposed feature would allow developers to organize templates in a more intuitive and efficient manner, without resorting to nested stacks or custom scripts. It simplifies template management and increases code readability, accelerating development, and reducing the potential for errors.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
What is the problem you are solving?
Developing large AWS SAM applications can lead to unwieldy and difficult-to-maintain template files. AFAIK Currently, there's no way to include other modules besides using nested stacks which doesn't quite seem to fulfill the purpose I'd like to use it for
Similar discussions?
Possibly #2734 but their problem seem to be primarily about hitting CF resource count limit and using multiple templates as a solution.
Describe the persona of someone who is facing this problem?
Developers who work on large complex serverless applications have a hard time finding related component in large template files (1000+ lines). They seek a more granular and efficient way to split templates to enhance code readability.
How do developers work around this problem today?
They resort to nested stacks or create custom scripts to combine templates manually. These workarounds can be cumbersome and error-prone, adding unnecessary complexity to the development process.
Describe your proposed solution?
Introduce a new mechanism within AWS SAM to allow template splitting at a more granular level, such as by individual resources or functions. Here's a conceptual example:
How is the proposed feature better than the workaround?
This proposed feature would allow developers to organize templates in a more intuitive and efficient manner, without resorting to nested stacks or custom scripts. It simplifies template management and increases code readability, accelerating development, and reducing the potential for errors.
Beta Was this translation helpful? Give feedback.
All reactions