Move argo-workflows to optional dependency
See original GitHub issueCurrently argo-workflows
is part of requirements.txt
that will be installed as a required package (see install_requires
field in setup.py
). We should move it to extra/optional requirements instead.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
A better way to specify optional dependencies · Issue #1781 ...
Common scenarios: Only start task when all dependent tasks succeed (supported by default); Start task when one of two dependencies succeeded.
Read more >Deployment with Argo Workflows - Kedro - Read the Docs
It allows you to easily run and orchestrate compute intensive jobs in parallel on Kubernetes. It manages the dependencies between tasks using a...
Read more >How to Configure an Artifact Repo for Argo Workflows - Pipekit
Learn what artifact repos are in Argo Workflows, their benefits, ... "config: |" key is optional in 2.7+! instanceID: my-ci-controller ...
Read more >argo-workflows 0.22.3 - Artifact Hub
This is a community maintained chart. It is used to set up argo and its needed dependencies through one command. This is used...
Read more >How To Combine Argo Events, Workflows & Pipelines, CD ...
What do we get if we combine events, workflows, GitOps, progressive delivery, and secrets management? The short answer is that we get ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That should be sufficient as long as CI passes.
Close via https://github.com/couler-proj/couler/pull/164