Trouble with configuring slack in dev env

[rollingmx]

Hello,

I try to test Slack app in dev env. I run Saleor inside Docker with Saleor platform and slack app locally. The Slack app is tunneled, so while installing I insert https://<url_tunnel>/api/manifest. I checked Upstash and the key is well saved while installation.

I see 400 error when the api tries accessing the https://<url_tunnel>/api/configuration.

My env file presented as such:

SECRET_KEY=12345

APP_LOG_LEVEL=debug

APL=upstash
UPSTASH_URL=<url>
UPSTASH_TOKEN=<token>

Any ideas on the route cause ? I tag @lkostrowski as you seems to be the biggest contributor.

[lkostrowski]

Hey, easiest way to get help would be checking our discord. You can also try to debug it yourself - slack app is just an example and it may not be working. Maybe logs show something valuable?

[ebarahona]

The example app is using a deprecated endpoint which does not exist, the correct API is the manifest endpoint which requires an admin Token to be called. I still ran into a bunch of other issues with APL, like you upstash is properly set and it's saving the config to Redis.

Workaround:
My workaround, was to just throw away the example slack app and add the webhook in the Saleor dashboard. Slack is expecting a specific "text" property in the payload, which Saleor has no way to customize, so I created a simple Node/Express app to act as a Webhook proxy, once the webhook is added in the dashboard, the app accepts the saleor POST and then formats to what I need so I can send off to slack or any other service.

Trying to customize Saleor has been a PITA

[ebarahona]

I've literally customized (hacked) Shopify checkout using injected JS scripts to completely customize the Shopify checkout and that has been much easier than working with the Saleor storefront source code.