[NR-344385] Support deployment of lambda templates from local setup #6
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
…d added s3 bucket arn addition as part of CI/CD
ahegdeNR
changed the title
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.
lambda-template yaml file has s3 bucket names in map hardcoded to fetch lambda code. This blocks developers from testing locally when they upload test files to a different bucket.
Hence modified CodeUri back to /src and modified CI/CD to change the template file with S3 object arn during release stage
Test run successfully here -> https://github.com/newrelic/aws-unified-lambda/pull/6/checks?check_run_id=33969865701