Summary

This is minor, but also really annoying when trying to run a bunch of workflows from the UI.

1. Go to /workflows
2. Click 'Submit new workflow'
3. Click in the 'select a workflow template' text area
4. Start typing

Issue: Your typing isn't refining the search.

I have to click again in the text dropdown for my typing to be effective.

Diagnostics

What Kubernetes

Current behavior

Right now, the connection string to Azure can be passed as a string at initialization or read AZURE_STORAGE_CONNECTION_STRING from the environment.

The connection string property is not serialized with the storage object. The only way to get this to work is to have AZURE_STORAGE_CONNECTION_STRING available when the flow is retrieved from storage. For most agent types, t

Description

When using the zbctl to create a worker we are able to set some flags, like the timeout of the job activation, but it is not clear from the help what the unit is and how the parameter should look like.

[zell camunda-cloud/ ns:bece6b37-3b9c-4fd0-8e79-4990cd0d057d-zeebe]$ zbctl create worker
Error: accepts 1 arg(s), received 0
Usage:
  zbctl create worker <type> [flag

This issue is intended to capture issues that need to be resolved for the test suite to pass on Windows.

• Manual Path Concatenations, e.g. https://github.com/scipipe/scipipe/blob/8113d5f546d29b862cab4b75b5fad475b1026c92/ip.go#L291
• Manual Filesystem Roots, e.g. https://github.com/scipipe/scipipe/blob/8113d5f546d29b862cab4b75b5fad475b

Summary

What happened/what you expected to happen?

We expect the container use the existing volume defined inside the workflow. Such as:
volumes-existing.yaml

example for testing:

import os

import couler.argo as couler
from couler.argo_submitter import ArgoSubmitter
from couler.core.t

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

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.