SUMMARY

I just faced an embarrassed problem that command st2 action list keeps return 503.

I tried st2 --debug action list and the result in line HTTP_PROXY(uppercase) was empty. This mislead me that the proxy info was set(which is not).

I finally found that the root cause is a lowercase http_proxy env variable was set in the system.

So I think it maybe more friend

In e2e test suite, we mock resource creation with fake client and verify the BotKube event generations.
https://github.com/infracloudio/botkube/blob/develop/test/e2e/notifier/create/create.go#L46

We need to add similar test cases to verify delete event handling.
We can use Delete API for Deleting a resource.

Add te

Once #1753 gets merged, we should really add the code_scanning_alert event so opsdroid can alert us when an alert is raised. You can see the github documentation on this event and the payload example to get an idea of what could be useful including in the event.

Related: yetibot/yetibot#371

Current API (AlphaVantage) is rate limited to 3 reqs per 5 min 😖

name: test
match: command
args:
  - var1

to

name: test
match: command
expose_args:
  - var1

This is consistent with expose_json_fields. So, any time we expose variable from within rules we would use the expose_ prefix.