kubescape / kubescape/workflows
Make `kubescape-cli-e2e-tests.yaml` workflows more generic
- Dominant language
- Python
- Stars
- 2
- Forks
- 10
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 5
Description
Can we make the reusable workflow more "generic"? For now, it requires some parameters that are close to **regolibrary** (eg. `DOWNLOAD_ARTIFACT_PATH`).
If I want to use this workflow to test **host-scanner**, I should provide the `DOWNLOAD_ARTIFACT_PATH` as well, even if it is not in the scope of the test.
So, if it's possible, we should make this input optional and modify the `systest-cli.py` command at the end of the pipeline to make it more "flexible" in order to provide additional `kwargs`, depending on the component that we are testing.
For example, we could use an input called `ADDITIONAL_KWARGS` that we are going to append at the end of the command, so we can test each component (**host-scanner**, **regolibrary**, etc.) specifying the needed `kwargs`.
This is not something of high priority, but we can see it as an improvement to make the reusable workflow more reusable.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the reusable kubescape-cli-e2e-tests.yaml workflow and the systest-cli.py command it invokes at the end of the pipeline. Trace how DOWNLOAD_ARTIFACT_PATH is passed and how workflow inputs become command arguments. Done means the workflow can be reused for host-scanner and regolibrary without irrelevant required inputs, while allowing component-specific additional kwargs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, python
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100