add lambda release workflow - main branch #994
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
mxiamxia
approved these changes
Jan 13, 2025
srprash
added a commit
that referenced
this pull request
Jan 14, 2025
Same as #994 but for the 1.33.x branch where we will be doing the release for ADOT v1 lambda layer from. By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
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.
Adding a manually triggered workflow to release the java lambda layers to multiple regions.
Tested by running the workflow in my fork, and confirmed that the layer was successfully published in
us-east-1.GH run: https://github.com/srprash/aws-otel-java-instrumentation/actions/runs/12738121465
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.