chore: add chainsaw e2e tests support - #3844
Conversation
Sorry, something went wrong.
Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
|
Thanks for doing this! We have a story in our backlog to check out chainsaw and have added your pr to it! Were you able to use the chainsaw migrate command? I know when I tried before it didn't like our scripts. |
Sorry, something went wrong.
|
Yup, it was all done with chainsaw migrate kuttl tests .... Only a few commands didn't pass (i fixed a bunch of bugs in v0.1.3 and a couple of other fixes will come in v0.1.4). BTW would you mind approving the workflows to check how it works ? |
Sorry, something went wrong.
| pgDataVolume: | ||
| pvcName: data-non-crunchy-cluster-0 | ||
| directory: data | ||
| postgresVersion: ${KUTTL_PG_VERSION} |
There was a problem hiding this comment.
The generate-kuttl Make target in the workflow is used to fill out these variables with certain variables that might be different between tests. We would need to update/duplicate that target for chainsaw or figure out a different way to use variables.
@eddycharly Does chainsaw have a concept of variables or variable expansion?
Sorry, something went wrong.
There was a problem hiding this comment.
v0.1.3 introduced support to pass arbitrary values to tests and v0.1.4 will come with a solution to inject values in the resource manifests so basically no need for a generate step anymore :)
Sorry, something went wrong.
Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
Signed-off-by: Charles-Edouard Brétéché <charles.edouard@nirmata.com>
Reviewers
At least 1 approving review is required to merge this pull request.
Checklist:
Type of Changes:
What is the current behavior (link to any open issues here)?
Tests are run with kuttl
What is the new behavior (if this is a feature change)?
Tests are run with both chainsaw and kuttl
Other Information:
Chainsaw is similar to kuttl but a lot more flexible and actively maintained.
If you need more infos 👇