Repository navigation
Fix Lambda Execution Streaming template configuration and generated CloudFormation resources - #4026
Open
Sidzeppelin95 wants to merge 4 commits into
Open
Sidzeppelin95 wants to merge 4 commits into
Sidzeppelin95 wants to merge 4 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Issue #, if available
No confirmed upstream issue number is available.
Description of changes
This pull request contributes a correction to the Lambda Execution Streaming quick-start template configuration that I previously encountered while working with AWS SAM CLI and CloudFormation.
During my investigation between May 10 and May 16, 2022, I encountered a template-processing and resource-generation problem while using the SAM quick-start workflow. The affected template did not produce the expected CloudFormation resource configuration. My historical notes describe an invalid SAM template or resource-generation error, but the exact original error message is no longer available.
I corrected the affected template configuration, generated the corresponding CloudFormation template artifact, and uploaded the corrected version to the AWS environment for further testing. I subsequently committed supporting template artifacts to my fork of the AWS Serverless Application Model repository.
The relevant supporting artifacts are:
The corrected template artifact defines an
AWS::Serverless::Functionresource namedHelloWorldFunction, including its code location, Python handler, runtime, and CloudWatch event configuration. It also exposes the generated function ARN and execution-role ARN through CloudFormation outputs. The associated resource documentation describes SAM-generated CloudFormation resources and their logical IDs.The intended change is to ensure that the affected quick-start template is correctly configured and can be processed into the expected CloudFormation resource structure. The upstream change should preserve the intended Lambda function configuration, event-source definition, code location, and generated resource references.
Scope and evidence: The files in my fork provide supporting context for the correction. Their visible commit dates are in July 2022, after the May 2022 experiment. I am therefore asking maintainers to review the artifact against the current upstream template and confirm the appropriate upstream change rather than treating the fork comparison alone as proof of the original defect or its cause.
Description of how you validated changes
According to my historical report, I corrected the template artifact and uploaded the resulting configuration to the AWS environment for further testing.
The available documentation records the