NH-75964 Add lambda production publish workflow #341
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
cheempz
approved these changes
Mar 21, 2024
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.
Adds lambda production publish workflow by adding a new
publish-destinput param to the existing workflow for staging. The input determines whether we use the existing staging publish role or the new role for prod. I've also renamed the reused workflows to make it a bit more clear which one is for dispatch:Publish APM Python lambda layer.Tested production publish resulting in layers ending in
1_6_0_2:1. Tested staging publish resulting in layers ending in1_6_0_2:2. I did these on another PR for the custom build branch and this PR ports over those changes formain.