You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Microsoft Teams incoming webhook (retiring October 1, 2024)
As this will be due in 2 days, I propose to address this rapidly to encourage people still using it to switch to the Power Automate ones.
Should we then...
remove both the webhookType parameter and the logic behind using the msteams option completely ? (Users that will update the package would face an error as this parameter would not be recognized)
deprecate it and replace all the code used when it is set to msteams with a warning indicating this method no longer works ? (Less brutal and dedicated message, while no impact on powerautomate users, as it is set by default and therefore not mandatory to mention it in the config file)
same as option 2, minus deprecation, in case new methods may emerge later ?
Or chose another way ?
If needed, I can provide a PR that would respect your choice
Thanks again for the awesome work !
The text was updated successfully, but these errors were encountered:
Hi @Az8th, deprecation has been extended to December 2025, so we can leave it as is. Although I like the deprecation notice on the msteams webhook type property.
Hello @estruyf,
It is stated in the readme that
As this will be due in 2 days, I propose to address this rapidly to encourage people still using it to switch to the Power Automate ones.
Should we then...
webhookType
parameter and the logic behind using themsteams
option completely ? (Users that will update the package would face an error as this parameter would not be recognized)msteams
with a warning indicating this method no longer works ? (Less brutal and dedicated message, while no impact onpowerautomate
users, as it is set by default and therefore not mandatory to mention it in the config file)Or chose another way ?
If needed, I can provide a PR that would respect your choice
Thanks again for the awesome work !
The text was updated successfully, but these errors were encountered: