Can documentation be added on how to unit test workflows using the luigi mock module ?
Couldn't find any examples in the lugi/examples folder either

Description

The current Grafana dashboard works well, but it is not obvious how to interpret each panel. While it's meant to serve a springboard for users to build their own dashboards, it's also used internally by the Zeebe team, and having non-documented panels leads to:

1. Steeper learning curve to onboard new developers
2. Older members have to still edit the panel to figure out wha

Hi,
I plan to run WALKOFF in a high-availability setup within a cluster.
Unforunately there is no documentation available.
Is this technically possible? Can you give me some hints in the right direction?
Otherwise I think this would be a great feature ;)

Why is this command giving an error even though it works ok on the command line: command 'curl http://www.rabbitmq.com/rabbitmq-signing-key-public.asc | sudo apt-key add'

see https://github.com/square/spincycle/blob/cbda5089abd89b68e2d6879a234b17ed9a912b8f/request-manager/api/api.go#L210

If we fail to start a request (probably because we couldn't send it to the JR), set the request to Failed instead of leaving it as Pending forever.

When starting proactive-server (/bin/proactive-server):

The resource manager with 2 local nodes created on pnp://172.20.10.2:6473[0/143]
The scheduler created on pnp://172.20.10.2:64738/
Starting the web applications...
mac os x
The web application /automation-dashboard created on http://172.20.10.2:8080/automation-dashboard
The web application /studio created on http://172.20.10.2:

currently all apps use the default container CMD command, there should be an ability to optionally change that to something else.

Expected/Wanted Behavior

It should be possible to add custom labels on an app level to running containers in addition to the existing Nebula labels of:

• "app_name"
• "orchestrator"

The existing Nebula labels should not be possible to be overwritten as so there should be some failsafe check to prevent overwriting them.

This should be an optional dict in the app config which default

Create a persistent storage docker container using Volume/Mount.

Context

For the toki-method-* method contract. We are passing in a context. Lets remove it since the superset of data and utilities is binded through this anyways.

Expected/Wanted Behavior

https://codecov.io/ should be added to know what the code coverage is as well as a badge of it

Actual Behavior

there is no code coverage tool