feat: stepactions for secure push to OCI registry #76
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.
JIRA
https://issues.redhat.com/browse/KFLUXDP-6
Description
This PR introduces 2 new stepactions:
secure-push-oci
, that scans the content of the specified directory, removes files that contain leaked information and pushes the directory content to the new/existing OCI artifact in quay.io, including the log from the leaktk CLI scanfail-if-any-step-failed
- which purpose is to exit with non-zero code, if any of the steps executed as a part of the tekton Task exited with non-zero code. This is useful in Tasks, where we want to save artifacts that were produced by a step, where the error was purposely ignored (usingerror: continue
field), but still want to fail the Task in the end, to give the user the correct job resultsAdditional comments
quay.io/konflux-qe-incubator/konflux-qe-tools:latest
image - it was updated and now it is save to merge itVerification