Argo marked as optional but E2E testing requires Argo for some test cases

Azure / orkestra

Orkestra is a cloud-native release orchestration and lifecycle management (LCM) platform for the fine-grained orchestration of inter-dependent helm charts and their dependencies

https://azure.github.io/orkestra

Other

105 stars 16 forks source link

Argo marked as optional but E2E testing requires Argo for some test cases #180

Closed AH-Dietrich closed 3 years ago

AH-Dietrich commented 3 years ago

Looking through the Orkestra website and docs it shows Argo as an optional tool, but the current E2E testing uses Argo part of the validation. It checks the Argo workflow to see if the bookinfo workflow was successful. Should we change the argo testing as optional or change the docs to say its required?

nitishm commented 3 years ago

@AH-Dietrich since it is only used in the CI pipeline for e2e testing and not required during production we can leave it marked as optional