Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix wrong discord parameter for botkube helm installation #126

Closed
huseyinbabal opened this issue Aug 16, 2022 · 0 comments · Fixed by #127
Closed

Fix wrong discord parameter for botkube helm installation #126

huseyinbabal opened this issue Aug 16, 2022 · 0 comments · Fixed by #127
Assignees
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@huseyinbabal
Copy link
Contributor

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 channel

Expected behavior

When I execute @BotKube ping on Discord, I should see pong message.

Actual behavior

It does nothing when I run @BotKube ping command

Steps to reproduce

  • Follow installation steps as described here
  • Run botkube commands on discord.
@huseyinbabal huseyinbabal added the bug Something isn't working label Aug 16, 2022
@huseyinbabal huseyinbabal self-assigned this Aug 16, 2022
@huseyinbabal huseyinbabal added the good first issue Good for newcomers label Aug 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant