go-workflow | Go version minimalist workflow engine | BPM library
kandi X-RAY | go-workflow Summary
kandi X-RAY | go-workflow Summary
Go version minimalist workflow engine
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of go-workflow
go-workflow Key Features
go-workflow Examples and Code Snippets
Community Discussions
Trending Discussions on go-workflow
QUESTION
Workflow:
...ANSWER
Answered 2021-May-13 at 19:02As mentioned in the comments, there are a couple issues with your manifests. They're valid YAML, but that YAML does not deserialize into valid Argo custom resources.
- In the Workflow, you have duplicated the
parameters
key inspec.templates[0].inputs
. - In the WorkflowTemplate, you have placed the
configMapRef
andsecretRef
names at the same level as the keys.configMapRef
andsecretRef
are objects, so thename
key should be nested under each of those.
These are the corrected manifests:
QUESTION
I am using Argo and have a question about the workflow of workflows example. (https://github.com/argoproj/argo-workflows/blob/master/examples/workflow-of-workflows.yaml)
UPDATED YET AGAIN
As pointed out below, it is a task that I need to view. So my question is now - How do I view the logs from a task?
My workflow completes without error, but does not produce the expected output. I would like to look at the logs of one of the containers within one of the workflows within the overall workflow, but I cannot get the syntax right I am using the following convention to get the logs from the relevant pod.
...ANSWER
Answered 2021-Apr-05 at 21:25The default container names on an Argo Workflows pod are init
, main
, and wait
.
I'm not sure what message-passing-1-t8749
refers to, but it might be the "step/task name."
QUESTION
I have a WorkflowTemplate "nyc-test-template" which I trigger via Argo Events and PubSub. So, if I publish a message {}
into the PubSub topic "argo-events-nyc" the template specified via a workflowTempateRef
is started. That does work just fine. Now I want to parameterize the to be started template.
My not-working draft looks as follows:
...ANSWER
Answered 2021-Mar-29 at 18:12You can use when
to toggle which template to use depending on a parameter.
Suppose I have two simple WorkflowTemplates like these:
QUESTION
The use case is that we think about triggering an Argo Workflow via Argo Events with PubSub. PubSub does not guarantee that a message is delivered only once. Is there an easy method to prevent a Workflow from being triggered again when it is running already?
Something like the concurrencyPolicy
setting for CronWorkflows.
To have something to look at - let's assume the whalesay Workflow:
...ANSWER
Answered 2021-Feb-23 at 18:20If you just need to make sure the Workflow doesn't run more than one simultaneous instance, use Argo's built-in synchronization feature.
QUESTION
I'm trying to access the Argo workflow archive via the REST API. The documentation states that I need to create a role and a token, so I that's what I did. A role with minimal permissions can be created like so:
...ANSWER
Answered 2021-Feb-15 at 21:59Looks like the role/serviceaccount/rolebinding created according to the docs only grant permissions to list Workflows in the argo
namespace (whether archived or not).
The namespace can be specified for the Archive like so:
QUESTION
I wanted to install an argo workflow template and workflow cron job as a helm chart. helm install command says the chart is installed. But I see only workflow template got deployed and cron job isnt.
Folder structure:
...ANSWER
Answered 2021-Feb-08 at 19:02Argo allows you to scale vertically by adding multiple workflow controllers. Each controller gets an "instance ID."
Your CronWorkflow specifies the fp
workflow controller instance.
QUESTION
I follow the Argo Workflow's Getting Started documentation. Everything goes smooth until I run the first sample workflow as described in 4. Run Sample Workflows. The workflow just gets stuck in the pending state:
...ANSWER
Answered 2020-May-14 at 16:15Workflows start in the Pending state and then are moved through their steps by the workflow-controller pod (which is installed in the cluster as part of Argo).
The workflow-controller pod is stuck in ContainerCreating. kc describe po {workflow-controller pod}
reveals a Calico-related network error.
As mentioned in the comments, it looks like a common Calico error. Once you clear that up, your hello-world workflow should execute just fine.
Note from OP: Further debugging confirms the Calico problem (Calico nodes are not in the running state):
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install go-workflow
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page