Cannot override user/icon/channel about slacktee

[Chikashi-Kato]

Ouch, this is a critical change for slacktee. Thank you for letting us know this, Robert.
I will test out the changes and update slacktee to address the changes.

[flyingbarron]

From what I can see, keeping that functionality will mean changing from incoming_webhook to one of the web APIs.
Let me know if I can help :)

[Chikashi-Kato]

Thank you, Robert! I'm still testing on my end, but I still can specify 'channel', 'name' and 'icon' through webhook. Since the webhook I used for testing have created long time ago, Slack may be keeping the backward compatibility for old webhooks.
I will create a new webhook and use it for my 2nd test.

It would be great if you can check when you created your webhook

[flyingbarron]

Less than 24 hours before opening this issue.

[Chikashi-Kato]

Got it, thanks! I think Incoming Webhook with the legacy 'Custom Integration' still supports the overwrite for 'channel', 'name' and 'icon' parameters, but migrating to Slack App is highly recommended.

https://api.slack.com/custom-integrations/incoming-webhooks

I think it might be a time to migrate to Slack App from the custom integration. Also, as you mentioned, we may be using Web API instead of incoming webhook for overwriting 'channel', 'name' and 'icon'. Some features of slacktee are already using the API and the migration shouldn't be too too difficult, I believe.

I will start some research for the migration, but if you already have some implementation ideas in your mind, please drop them here!

[Chikashi-Kato]

Sorry for not posting an update for a while. I was busy in last 2 weeks and couldn't find a time to work on this issue. I am still trying to implement it by myself, but it would be really appreciated if anyone can submit a PR addressing this issue!

[Chikashi-Kato]

Add the logic posting messages through APIs and deprecated incoming webhook.