Resources in parallel unless dependson
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
There was strong feedback at PS & DevOps Summit that rather than having a Parallel group type, resources should just always run in parallel unless "DependsOn" expresses a relationship so resource 1 must complete before resource 2 can start. The intention is to have configuration behave in the same way that Azure deployments behave, hoping that new users might have intuition that the two could work the same way.
After sleeping on the question, my main concern is that we don't really know which resources will work well when run in parallel, and some might cause problems. We could express it as a capability but that would create work for the community.
Tagging a few people to invite them to continue the discussion. Thank you!
@alexandair, @jaykul, @brwilkinson
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the discussion in this issue; no implementation files, tests, or entry points are identified. The proposal needs an agreed resource execution model and defined acceptance criteria before implementation can be scoped, with completion requiring that model to be decided and implemented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, rust
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100