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

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

Describe the bug

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

Receive events from MSK with IAM auth config https://docs.aws.amazon.com/msk/latest/developerguide/iam-access-control.html

It would be nice if doit could use as many processes as there are CPUs instead of only a hardcoded number.

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

Currently, the autogenerated Archive choice still includes let bindings. Given that we control them this is somewhat redundant and we could just omit them to speed things up slightly.

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

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%|

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

Follow up for #197 and #215

• Fix the ORDER BY issue so that we don't accidentally overwrite extra dispatch IDs https://github.com/AgnostiqHQ/covalent/pull/215/files#diff-d5a1b52ef809a88edbb01367cf4a161ddc0b9ce35c885981d8a8363cb0588949R151
• Figure out why middleware doesn't work https://github.com/AgnostiqHQ/covalent/pull/215/files#diff-d5a1b52ef809a88edbb01367cf4a161ddc0b9ce35c8859