-
Notifications
You must be signed in to change notification settings - Fork 150
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move init container release from lambda to GHA #2179
Move init container release from lambda to GHA #2179
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should move this into its own workflow, to be run at the end of our release process.
I'm not super familiar with the init container process, but it looks like these changes will cut the init container release immediately. publish_release
is the start of our release process. The agent jar generally isn't available on the downloads site, where the init container is looking for it, until a few days after this action is run.
Co-authored-by: Kate Anderson <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, thank you! Will merge myself once release activities conclude this week.
Merging with AIT failures (token issue). New workflow action that AITs don't cover. |
Overview
We are getting rid of the internal auto-layer-releases repo and moving creating of the release tags into each agent's GHA deploy flow.