feat: Implement dynamic Kubescape versioning in GitHub Action #72
+70
−15
Conversation
This file contains hidden or 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
Refactor the GitHub Action to build the Docker image at runtime using a user-specified version of `kubescape-cli`. * Introduce a build argument `KUBESCAPE_VERSION` in the `Dockerfile` to dynamically set the base image version. * Convert the action to a composite action in `action.yml`. * Add a mandatory `version` input to `action.yml` to allow users to specify any `kubescape-cli` version or 'latest'. * Implement version resolution logic in `action.yml` to fetch the latest tag if `version` is set to 'latest', using the `github.token` for authentication. * Update the build step in `action.yml` to pass the resolved version as the `--build-arg KUBESCAPE_VERSION` to `docker build`. * Update the run step in `action.yml` to use the resolved version tag for the `docker run` command. * Rewrite `update.sh` to fetch the latest release tag and update the `KUBESCAPE_VERSION` argument in the `Dockerfile` using `sed`. Signed-off-by: Emre Şafak <3928300+esafak@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Why
Users should not have to wait for someone to update this action, which unfortunately happens very rarely, to benefit from updates to the main utility. We refactor the GitHub Action to build the Docker image at runtime using a user-specified version of
kubescape-cli.What this does
KUBESCAPE_VERSIONin theDockerfileto dynamically set the base image version.action.yml.versioninput toaction.ymlto allow users to specify anykubescape-cliversion or 'latest'.action.ymlto fetch the latest tag ifversionis set to 'latest', using thegithub.tokenfor authentication.action.ymlto pass the resolved version as the--build-arg KUBESCAPE_VERSIONtodocker build.action.ymlto use the resolved version tag for thedocker runcommand.update.shto fetch the latest release tag and update theKUBESCAPE_VERSIONargument in theDockerfileusingsed.Testing
I successfully ran the refactored action on my fork: https://github.com/esafak/kubescape-gha/actions/runs/20386459620/job/58588241646
Notes
The
kubescape-fix-pr-reviewsworkflow, which I did not touch, fails with the typo "Scannign scope is not specified. Scanning all frameworks".