feat: support the severity threshold input #11
Merged
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
This commit adds support for specifying the severity threshold as an input for the Github Action.
vladklokun
commented
Sep 21, 2022
dwertent
approved these changes
Oct 3, 2022
dwertent
pushed a commit
that referenced
this pull request
Oct 3, 2022
* feat: support the severity threshold input (#11) This commit adds support for specifying the severity threshold as an input for the Github Action. Co-authored-by: David Wertenteil <dwertent@armosec.io> * Build and publish a "github actions" image (#15) * adding account ID support * Adding example * gh doc example * use avinash actions * comment out account * testing examples * fixed control ID * fixed checkout * use single file * Support non-root user * update junit * update org name * adding "needs" * update working dir * Run as root * changed threshold * change to a single step * update threshold * cosmetic changes * update example * remove default failedThreshold * update INPUT_FAILEDTHRESHOLD * adding default failedThreshold to the workflow * remove failedThreshold from actions * printing path * Gh workflows (#1) * adding release * trigger * remove deps * adding push to command * update ks base image * update org * rename file Co-authored-by: Vlad Klokun <vladklokun@users.noreply.github.com>
dwertent
pushed a commit
that referenced
this pull request
Oct 27, 2022
* adding account ID support * Adding example * gh doc example * use avinash actions * comment out account * testing examples * fixed control ID * fixed checkout * use single file * Support non-root user * update junit * update org name * adding "needs" * update working dir * Run as root * changed threshold * change to a single step * update threshold * cosmetic changes * update example * remove default failedThreshold * update INPUT_FAILEDTHRESHOLD * adding default failedThreshold to the workflow * remove failedThreshold from actions * printing path * Gh workflows (#1) * adding release * trigger * remove deps * adding push to command * update ks base image * update org * feat: support the severity threshold input (#11) This commit adds support for specifying the severity threshold as an input for the Github Action. Co-authored-by: David Wertenteil <dwertent@armosec.io> * rename file * Update action url Co-authored-by: Vlad Klokun <vladklokun@users.noreply.github.com>
dwertent
pushed a commit
that referenced
this pull request
Nov 6, 2022
* adding account ID support * Adding example * gh doc example * use avinash actions * comment out account * testing examples * fixed control ID * fixed checkout * use single file * Support non-root user * update junit * update org name * adding "needs" * update working dir * Run as root * changed threshold * change to a single step * update threshold * cosmetic changes * update example * remove default failedThreshold * update INPUT_FAILEDTHRESHOLD * adding default failedThreshold to the workflow * remove failedThreshold from actions * printing path * Gh workflows (#1) * adding release * trigger * remove deps * adding push to command * update ks base image * update org * feat: support the severity threshold input (#11) This commit adds support for specifying the severity threshold as an input for the Github Action. Co-authored-by: David Wertenteil <dwertent@armosec.io> * rename file * Update action url * made small change * chmod * update ks image version Co-authored-by: Vlad Klokun <vladklokun@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What this PR changes?
This PR adds support for specifying the severity threshold as an input for the Github Action.
Requires kubescape/kubescape#838