Is your feature request related to a problem? Please describe.
Because today we have hardcoded the RPC names to be "cadence-frontend/history/matching".
See https://github.com/uber/cadence/blob/befd8954e06a1ee178d6d3eb168628282053d95d/cmd/server/cadence/server.go#L110

So it's useless to allow putting a different config. In fact, only "cadence-frontend" will work.

Proposed Solution

An addition to Add python warning if install a pack that only supports python 2 #5037 PR and Python 2 Deprecation Game Plan, apart of warning for pack install, we might need to also warn users that's running StackStorm in py2 environment.

I'd suggest to show and log that warning for each st2

The existing HTTP Request Trigger activity needs to be enhanced so that it allows users to have it generate a SAS token. The workflow will then only be triggered if the provided SAS token is valid. This prevents the workflow from being invoked by anyone other than those who have the full URL (including the SAS token appended as a querystring).

Is your feature request related to a problem? Please describe.
SNS endpoint subscriptions must expose a public facing HTTP server ( unless I missed something ) and therefore make it possible for untrusted sources to post messages to the event bus as long as the message comply with basic message format.

Describe the solution you'd like
The SNS source should verify the signature of the

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

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

Inspired by common-workflow-language/common-workflow-language#125 (comment)

And if not, do we want it to?

similar to #785 but for docker pull