[Question] Is it planned to have "step calling steps" feature ?

[nvetel]

Describe your question

Hello,

On a project I'm contributing with, we design our tests to have reusable steps. But what we see is that sometime a step is expected to be called on a test, and sometimes it has to be called in a biggest step involving the small one, but we need to duplicate the code in the biggest step.

What is the proper way to have such "russian doll" feature with steps or maybe operations, and avoid code duplication ?
If this is not possible, is there any feature covering those use cases planned in the future ?

Thanks

chainsaw version Version

v0.2.13

Additional context

No response

[eddycharly]

Thanks for reporting @nvetel !
Can you share a simple example of what you are trying to achieve ?

[nvetel]

Hello @eddycharly,

On my project, we are developing network components on kubernetes (CNI, dataplane, etc)
A typical test on this project, is to build a network topology: a network, and workloads attached and communicating over that network, and test features on that network (ping, filtering traffic, policing, etc.).

We built steps for unitary network elements, sometimes with a network attachement definition dedicated, often with assertions and checkings, for example:

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: StepTemplate
metadata:
  name: create server
spec:
  try:
  - apply:
      file: resources/net-attach-def-pod-server.yml
  - apply:
      file: resources/pod-server.yml
  - assert:
      resource:
        apiVersion: v1
        kind: Pod
        metadata:
          name: pod-server
        status:
          (conditions[?type == 'Ready']):
            - status: "True"

We use those steps on tests with dedicated topology. But we build the same "classical topology" in multiple tests. So we created a step building this "classical" topology, copying the code from unitary block steps.
What would like to avoid this code duplication by reusing unitary block steps in our topology steps, for example:

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: StepTemplate
metadata:
  name: basic topology
spec:
  try:
  - apply:
      step: resources/step-pod-server.yml
  - apply:
      step: resources/step-pod-client.yml

[eddycharly]

Got it, that's an interesting idea, thanks for bringing it up.
It's not supported yet but i'll keep thinking about it.