Issue:
Currently, Globals are applied to all functions defined in the AWS SAM template, which can cause issues when users want to customize specific functions without affecting the others. This issue has been reported by some users, and a possible solution is to introduce a new property to the function definition that allows users to selectively ignore Globals for specific functions.
Proposed Solution:
Add a new property to the function definition, such as "IgnoreGlobals" or similar, that allows users to specify whether or not Globals should be applied to that particular function. This would give users more control over how Globals are applied in their AWS SAM templates and would make it easier to customize functions without affecting the entire template.
Please share your thoughts or feedback on this proposal. Thank you!
Issue:
Currently, Globals are applied to all functions defined in the AWS SAM template, which can cause issues when users want to customize specific functions without affecting the others. This issue has been reported by some users, and a possible solution is to introduce a new property to the function definition that allows users to selectively ignore Globals for specific functions.
Proposed Solution:
Add a new property to the function definition, such as "IgnoreGlobals" or similar, that allows users to specify whether or not Globals should be applied to that particular function. This would give users more control over how Globals are applied in their AWS SAM templates and would make it easier to customize functions without affecting the entire template.
Please share your thoughts or feedback on this proposal. Thank you!