close
The Wayback Machine - https://web.archive.org/web/20220427053844/https://github.com/topics/workflow-automation
Skip to content
#

workflow-automation

Here are 201 public repositories matching this topic...

budibase
melohagan
melohagan commented Apr 22, 2022

Describe the bug

  • Not all examples are using the correct handle bar helper
  • There is a mix of with/out spaces between commands and handle bars. They should probably have the spaces, as they are included when injecting.
  • Some helpers have no examples
  • The helpers are ordered alphabetically within groups (e.g. Math helpers) but there is no separation or indicator of these groups.
bug good first issue sev3
longquanzheng
longquanzheng commented Feb 5, 2021

Is your feature request related to a problem? Please describe.
Need to search using LIKE operator with search attributes? eg, WorkflowType LIKE workflowType-prefix.*
Right now the workflowType is using keyword type for performance reason so it doesn't support wildcard search.

https://www.elastic.co/guide/en/elasticsearch/reference/current/keyword.html

keyword fields are untokeniz
feature up-for-grabs good first issue
samarabbas
samarabbas commented May 15, 2021

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

nooraangelva
nooraangelva commented Aug 4, 2021

Summary

What change needs making?
Example script on how to use created secret successfully.
I have tried myself using the following code from test
It creates a secret successfully but fails to echo the secrets value.

Use Cases

When would you use this?
when I n

enhancement good first issue help wanted
obsei
gh-action-pypi-publish
tzulberti-jampp
tzulberti-jampp commented Feb 19, 2020

I am not sure if this belongs here, but I am having an issue when using this Github Action.

This is the link to the github run that failed:
https://github.com/jampp/migratron/pull/25/checks?check_run_id=456554120

and the content is:

Uploading distributions to https://test.pypi.org/legacy/
Uploading migratron-1.1.0-py3-none-any.whl

  0%|          | 0.00/30.5k [00:00<?, ?B/s]
100%|
enhancement help wanted good first issue

This Python framework helps you share artifacts, knowledge and experience in a more reusable, automated, portable, reproducible and unified way. It transforms Git repositories, Docker containers, Jupyter notebooks and zip/tar files into an open database of reusable artifacts and automations with a unified API and extensible meta descriptions.

  • Updated Apr 26, 2022
  • Python
odin
tmkontra
tmkontra commented Aug 2, 2020

Describe the bug
Deploying a new job, then pulling logs via the CLI results in a panic (SIGSEGV).

To Reproduce

  1. odin deploy -f test.job.yaml
  2. odin 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
bug good first issue
jimi

Jimi is an automation first no-code platform designed and developed originally for Security Orchestration and Response. Since its launch jimi has developed into a fully fledged IT automation platform which effortlessly integrates with your existing tools unlocking the potential for autonomous IT and Security operations.

  • Updated Apr 15, 2022
  • Python
covalent

Improve this page

Add a description, image, and links to the workflow-automation topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the workflow-automation topic, visit your repo's landing page and select "manage topics."

Learn more