add: support staging and production lambda ARNs #123
Merged
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
lakshayman
approved these changes
Sep 15, 2024
MehulKChaudhari
deleted the
setup-staging-lambda-arns-template&pipeline
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.
Date: 15 September 2024
Developer Name: @MehulKChaudhari
Issue Ticket Number
#121
Description
The Lambda ARNs used to interact with other Lambda functions for modifying concurrency limits are currently hardcoded for the production environment in the template.yaml file. This hardcoding leads to potential issues when working in different environments (e.g., staging) where different ARNs are required. This makes it difficult to manage and deploy changes across environments without manual updates to the template.
Documentation Updated?
Under Feature Flag
Database Changes
Breaking Changes
Development Tested?