You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Generally the scenario manifests created via Chaos-Center contains an install-chaos-experiments step, which contains definition for all experiments users are going to run as part of that scenario. At the time of implementation of this feature (litmusctl create scenario), it was decided to use install-chaos-experiments step to fetch names of all experiments, users have added in the manifest.
But this can't be always the case, users may not have install-chaos-experiments step in their manifests while scheduling it via litmusctl.
When we upload a manifest in frontend, we had enhanced the logic in frontend by searching for templates which contains kind: ChaosEngine & fetch their names. Since a template containing kind: ChaosEngine denotes a chaos experiment. Same can be done in litmusctl making it independent of install-chaos-experiment.
Generally the scenario manifests created via Chaos-Center contains an
install-chaos-experiments
step, which contains definition for all experiments users are going to run as part of that scenario. At the time of implementation of this feature (litmusctl create scenario), it was decided to useinstall-chaos-experiments
step to fetch names of all experiments, users have added in the manifest.But this can't be always the case, users may not have
install-chaos-experiments
step in their manifests while scheduling it vialitmusctl
.When we upload a manifest in frontend, we had enhanced the logic in frontend by searching for templates which contains
kind: ChaosEngine
& fetch their names. Since a template containingkind: ChaosEngine
denotes a chaos experiment. Same can be done in litmusctl making it independent of install-chaos-experiment.For reference, how it's done in frontend - https://github.com/litmuschaos/litmus/blob/643f3bffb87a20fee209a77b842ad7eda01d1e54/litmus-portal/frontend/src/utils/yamlUtils.ts#L250
The text was updated successfully, but these errors were encountered: