argoproj / argoproj/argo-workflows

container set next steps: enhanced depends logic

Open
#5,281 0 comments 0 reactions 0 assignees View on GitHub
area/templates/container-set
Dominant language
Go
Stars
17k
Forks
3.7k
Avg merge
1d 20h
Merged PRs (30d)
138

Description

MVP/v1.0 implementation only supports basic declarative `dependencies. This is limited compared to DAG templates:

* Cannot have partial dependencies - i.e. start whenever one of the dependencies have started
* Dependencies must exit 0 - i.e. what about starting just when the dependency is just complete, regardless of exit code?

See #2551

Contributor guide

Open the contributing guide

Research direction

Start with #2551 and the current MVP/v1.0 container set next-steps implementation. Compare its basic declarative dependencies with the DAG-template behavior described here; done means agreeing on and implementing partial-start and completion-regardless-of-exit-code semantics.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
devops, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.