Particularly EXECUTOR_IMAGE

EXECUTOR_IMAGE=argoproj/argoexec:latest workflow-controller

CLI flags take precedence obviously.

It seems we have a user-contributed task for SodaSQL that we don't expose in our API documentation, making it very hard to discover; task definition and docstrings here: https://github.com/PrefectHQ/prefect/blob/5de58efaba956b431335d99acab07eaf6a362e1b/src/prefect/tasks/sodasql/sodasql_tasks.py

We should add this to our reference docs using [our development guidelines](https://docs.prefect.io/c

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

Describe the bug

We have several commands which should return an empty response like:

• Fail job
• Complete job
• Cancel instance
• Resolve incident
• etc.

But instead of returning an object (which would be expected, since it is part of the interface) it is returning null.

The following fails:

val fai

Summary

Validate Helm Repos as the user adds them.

Motivation

Adding an invalid repo will stop chart deployment as argocd validates all the helm repos before deploying any helm chart.

Proposal

If repo url is : https://helm.devtron.ai/

https://helm.devtron.ai/index.yaml should return a 200 http status

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