feat: add chainsaw scorecard test support #6676
Conversation
Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
openshift-ci
bot
added
the
do-not-merge/work-in-progress
| @@ -0,0 +1,37 @@ | |||
| # Build the scorecard-test-chainsaw binary | |||
| FROM --platform=$BUILDPLATFORM golang:1.21 as builder | |||
There was a problem hiding this comment.
If Operator-SDK has the intention to begin to support chainsaw, I think you will need to add an e2e test for those as well. see; https://github.com/operator-framework/operator-sdk/blob/master/test/e2e/go/scorecard_test.go
There was a problem hiding this comment.
I can work on that later today :)
There was a problem hiding this comment.
Before working on it, I suggest contacting the SDK maintainers in the operator-SDK-dev slack channel to see if they are willing to add it to the project.
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci
bot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci
bot
added
lifecycle/rotten
|
/remove-lifecycle rotten |
openshift-ci
bot
removed
the
lifecycle/rotten
Description of the change:
Add chainsaw scorecard test support.
Motivation for the change:
Chainsaw is a tool to run operators/controllers tests.
It is similar to kuttl but with a more modern and flexible approach.
It would be nice to add chainsaw scorecard into operator-sdk.
Checklist
If the pull request includes user-facing changes, extra documentation is required:
changelog/fragments(seechangelog/fragments/00-template.yaml)website/content/en/docs