Right now these slash commands are queued into SQS and then consumed by the app. This was for a couple reasons:
The server we run the app on in our office isn't accessible from the outside world
Using AWS (API Gateway) removes the need to manage SSL certs for HTTPS, which is a requirement for slash command endpoints.
However, if the server could be made public, the SQS pipeline could just be replaced with an HTTP proxy to the built-in HTTP server here. If anyone wants it, it'd be a worthwhile enhancement.
Right now these slash commands are queued into SQS and then consumed by the app. This was for a couple reasons:
However, if the server could be made public, the SQS pipeline could just be replaced with an HTTP proxy to the built-in HTTP server here. If anyone wants it, it'd be a worthwhile enhancement.