ci: Optimized the lambda layers and k8s init containers post release workflow #2915
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
bizob2828
changed the title
mrickard
approved these changes
Jan 31, 2025
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.
Description
In #2848 we moved the publishing of github releases of
newrelic-lambda-layersandnewrelic-agent-init-containerto a post release workflow, instead of a lambda cron that checked if any new releases of agent existed. I overlooked when I first reviewed that it doesn't check if Create Release was a success so I added that logic. I also removed some unnecessary jobs to setup node, install deps and configure git. The reason is Node.js isn't being used here, we just cat the package.json to get the version and then rely onghto create releases. Also since it auths toghcli with a token we don't have to set up the username/email.