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

Summary

"This is pretty confusing: are the types here config types? the types of the resource? if the former, they don't seem right; if the latter, it's not helpful to have Any for essentially any meaningful resource -- we should either allow the user to give us a hint of what type the resource is, or cut this f

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

Is your feature request related to a problem? Please describe.
Each event received/emitted from event sources already has an event ID attached, so that it can be used in Sensor to achieve uniqueness, this ID is currently generated automatically. For some of the event sources like Kafka, we can extend the feature to generate a unique ID based on the original message, so that even there's a dup

Describe the bug

The section on creating a service account in the Google Cloud console is out of date

With #11315 done, we can do some small optimizations:

• NonEmpty
  • if it makes a difference, redefine pour to abstract over IterableFactory and MapFactory, if those implementations do optimization for same-type conversions
  • redesign pour's API to put the factory type first, no more tricky currying
  • just use toSeq for toSeq
  • define collect, map, and

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

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.

Currently each Observer support state management.

Obsei store state in any of sqlalchemy supported database on schema mentioned in WorkflowTable class.

There is example also exist to show it's capability.

State m

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

The files on PyPI have these hash values:

• SHA256
• MD5
• BLAKE2-256

If print the hash values, people can easily verify whether the file on PyPI was automatically uploaded by CI script.
It is best to print a pretty-print table.

As of alpha 2.685 there's a new action trigger_named_async_without_response which can be used in favor of trigger_named. Wrapper does not operate on trigger response anyway, so using the new method which works better for broader spectrum sounds like a good idea. More on that here: https://community.folivora.ai/t/floating-html-settings-menu/5788/44?u=worie

the CBU example scripts demonstrate some really cool aa functionality that isn't really covered anywhere else, since we don't have much documentation. It's a shame that only people at CBU can run them (and in fact not even that many people at CBU since many of them use the CamCAN dataset).

It would be useful if t

We have a handful of tests that require sleeps to get things to happen in an expected order. This is obviously not ideal. We need a reasonable way to wait for certain things to happen deep in the internals of the code and expose that to tests in a way that doesn't require making all sorts of ugly changes purely for that ability.

If we could leverage tracing for this, that'd be nice. We could ju