workflow-engine
Here are 353 public repositories matching this topic...
Hello!
I've found an issue here:[Bitbucket Storage](https://docs.prefect.io/api/latest/storage.html#github) is a storage option that uploads flows to a Bitbucket repository as .py files.
Page reference: https://docs.prefect.io/orchestration/flow_config/storage.html#bitbucket
First, the link is incorrect. Second, should the line read more like Github where it references the repository
This feature includes following sub-features:
- add Store.Db, default "dtm"
- remove Store.TransGlobalTable Store.TransBranchOpTable
-
Updated
May 18, 2022 - Elixir
Need to fix this TODO in the code:
// TODO: we need to consider adding execution time to mutable state
// For now execution time will be calculated based on start time and cron schedule/retry policy
// each time DescribeWorkflowExecution is called.
https://github.com/temporalio/temporal/blob/master/service/history/historyEngine.go#L1184
If you are using Conductor at the company you work with, add the name of your company and your Github handle to the list at https://github.com/netflix/conductor/blob/main/WHOSUSING.md
-
Updated
May 20, 2022 - Java
-
Updated
May 12, 2022 - C#
-
Updated
May 19, 2022 - Java
Is your feature request related to a problem? Please describe.
It's not especially common to generate a certificate file which includes its own CA chain as well. The common case would be to have a shared CA chain file for each node, and then each node gets its own certificate (which other nodes cannot access). The Java client, for example, already works like this. Right now, for inter-clust
-
Updated
Apr 11, 2022 - Python
-
Updated
May 20, 2022 - Groovy
-
Updated
May 7, 2022 - Python
-
Updated
May 20, 2022 - Python
-
Updated
Apr 19, 2020 - Java
-
Updated
Mar 31, 2022 - Clojure
-
Updated
Oct 21, 2021 - Python
Group support
We should have a group support to handle permissions access from a LDAP, SSO, ...
allowed_resolvers_groups on templates for example.
admin_groups on configuration for example.
-
Updated
May 16, 2022 - JavaScript
-
Updated
May 20, 2022
-
Updated
May 16, 2022 - Python
-
Updated
May 20, 2022 - JavaScript
-
Updated
Aug 13, 2021 - Go
-
Updated
May 20, 2022 - JavaScript
Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).
To Reproduce
odin deploy -f test.job.yamlodin log -i {job_id}
vagrant@vagrant:~/odin$ odin log -i dea194794589
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x40 pc=0x79c764]
goroutine
-
Updated
Apr 27, 2022 - Java
Improve this page
Add a description, image, and links to the workflow-engine topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the workflow-engine topic, visit your repo's landing page and select "manage topics."
PodPriorityshould be deprecated from workflow spec since Kubernetes usesPodPriorityClassto indicate the importance and priority of a pod relative to others.https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/
https://github.com/argoproj/argo-workflows/blob/178bbbc31c594f9ded4b8a66b0beecbb16cfa949/pkg/apis/workflow/v1alpha1/workflow_types.go#L345-L346