Probe Reusability

[ggolub]

Would like the ability to make probes more generic and also portable. This involves two things

1. Ability to export/import probes as .yaml, much like you can do with the experiments.
2. Capability to use templates. For example, We have numerous http probes with the same health check. The only difference is the internal DNS for each. Would be helpful not to have to redefine the "same" probe over and over again. Instead, some template placeholder could be useful.

[rogeriofbrito]

As for the first item, currently the probe definition is loaded to ChaosEngine yaml template at the time of experiment is triggered. I think that the probe part of ChaosEngine could already be placed at the moment the experiment is saved and a new revision is created. In this way, the probe would be part of the entire experiment yaml and there would not be no need to load the probe details when experiment is triggered.

[ggolub]

That doesn't address the need for export/import. If I have multiple installations of LitmusChaos I need a way to migrate the probes between them. Currently cannot do so. In addition, if I use HTTP probes that are slightly different, it would be fare more efficient to create my probe, export it, tweak the .json/.yaml, and import it rather than repeat the creation numerous times.

[AkaiRingo]

i second this issue. currently at the same situation.