mudler / mudler/yip

Make steps that ignore the outcome or can run in background

Open
#93 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
113
Forks
34
Avg merge
14h 10m
Merged PRs (30d)
5

Description

Seems like a good addition could be steps that we just dont wait for. A fire and forget lets call it.

Could be implemented on the commands for now as that seems the most obvious use case.

Also it could be nice to have them run on the background. Which means still get the output but dont block other steps from running.

stages:
    default:
      - name: "Run some commands"
        type: {ignore-exit, default, background}
        commands:
          - sleep 20 && echo "done"

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing how stages execute their command steps and how the YAML type value is handled. Define the behavior for ignore-exit and background, including failure handling, output, and whether later steps continue; done means the example configuration works without blocking as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.