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
Recent version of botkube (v0.12.4) expects --set communications.discord.botid, but it is --set communications.discord.botID in the current doc. This breaks discord integration in a way that I cannot see kubectl command responses in Discord channel
Expected behavior
When I execute @BotKube ping on Discord, I should see pong message.
Description
Recent version of botkube (v0.12.4) expects
--set communications.discord.botid
, but it is--set communications.discord.botID
in the current doc. This breaks discord integration in a way that I cannot see kubectl command responses in Discord channelExpected behavior
When I execute
@BotKube ping
on Discord, I should see pong message.Actual behavior
It does nothing when I run
@BotKube ping
commandSteps to reproduce
The text was updated successfully, but these errors were encountered: