Eugen

@jk464 Yeah, let's reassign this PR to the `v3.9.0` roadmap It'll be a reminder that `requests` will need an update after dropping the py3.6.

@nzlosh Any next steps? Do we need to pin `yaql` in the requirements to fix it?

Adding an update here as some things are outdated now (sorry for that!). We're using CircleCI for free these days and the container we're using is `large` as well: https://github.com/StackStorm/stackstorm-k8s/blob/b45c85937e08f97cd697e66d764763835fb9e1a3/.circleci/config.yml#L50-L55...

@guzzijones makes sense to revive this PR? I'm guessing the dependency update might be helpful here.

@rush-skills good call, the changes to the Governance requires an approval of `50%+` from the TSC members, according to https://github.com/StackStorm/st2/blob/master/GOVERNANCE.md#how-decisions-are-made so yeah, this PR is missing votes to be merged.

You might be surprised https://github.com/hubot-scripts/hubot-shipit/pulls :smiley:

@gr2m @technicalpickles Please take an action and click the Merge button. We have 6 PRs and 5 Issues opened since 2016 all about broken images. Please fix the squirrels!

I hope this rate-limiting would be switched off by default and can be enabled `on` only by those who really need it. Otherwise when enforced it can only bring much...

Agree, documenting `nginx`-based rate-limiting sounds like the best performing and easy enough solution where user has some good options to control.

@zsmanjot That's an interesting idea. I think the feature to disable/enable an action/workflow from UI would be helpful. At least there's a meta for it: https://github.com/StackStorm/st2/blob/d374b92f0dbf6b26c5dfdcffd594ecbd0800d635/contrib/examples/actions/orquesta-ask-consecutive.yaml#L4-L6 If you or your...