ci: inject dockerfile dependency versions from workflow #1247
+115
−22
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
zerok
force-pushed
the
zerok/inject-dependency-versions-from-workflow
branch
18 times, most recently
from
7dd19dc
to
6849ae6
Compare
zerok
force-pushed
the
zerok/inject-dependency-versions-from-workflow
branch
from
6849ae6
to
6199ceb
Compare
dylwylie
approved these changes
Nov 26, 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.
We are running into some hard to some API limits (probably) within the Dockerfile while determining the version of the latest kustomize and helm releases. This change moves those queries out into the workflow so that we can inject alternative GITHUB_TOKENs if we must.