Summary

From an archived workflow, click on "Resubmit" in the UI

The created workflow do not have the appropriate labels

/!\ the bug happens only for archived workflows (when you resubmit a "normal" workflow, the labels are kept)

Be cautious, some labels should not be copied (like workflows.argoproj.io or workflows.argoproj.io/phase)

however, the labels placed manually by the us

Opened from the Prefect Public Slack Community

elliot: Hey folks is anyone else getting a deprecation warning on marshmallow? Something like:

...
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198
/home/rof/.pyenv/versions/3.9.1/lib/python3.9/site-packages/marshmallow/fields.py:198: RemovedInMarshmallow4Warning: Passing fi

Is your feature request related to a problem? Please describe.
There is an optional config for namespace called "sampled retention days" that can be specified when create a namespace. It was created long ago as workaround for long retentions before long term archival was available.

Describe the solution you'd like
We should get rid of the sampled retention.

**Describe alternatives

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

As reported by @jonalv , it can be confusing what is happening when if the globber pattern does not catch any files.

The suggestion is to:

• Log when the globber starts, with the pattern used
• Issue a warning if the globber doesn't match any files at all

Summary

The current implementation does not allow creating templates specifying the parallelism field as per the Argo spec.

Use Cases

Many possible use cases, my current one is limiting the amount of parallel nodes running a certain template so as to save

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.

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