refactor: apply a common function to get a aws config in aws lambda and apply synchronized use statements and an explicit client #123
Conversation
This file contains 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
bryan-stclab
added
target: scaling-component
pueding
approved these changes
Aug 2, 2023
pueding
deleted the
122-apply-a-common-function-to-get-a-aws_config-in-aws_lambda
branch
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.
Types of changes
What this PR does / why we need it:
With a common function to retrieve the aws_config, it is necessary to apply it in the AWS Lambda scaling component.
Which issue/s this PR fixes
#122, and #83
How Has This Been Tested?
I tested with exist code in core/wave-autoscale/src/scaling_component/aws_lambda_function.rs
Checklist: