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
A user needs to know whether the Botkube installation process is successful or not, and be informed of any errors. The current helm install process will time out if there are problems and the user needs to look at the pod logs to troubleshoot the issue. There are some common pitfalls with Botkube configuration that cause the installation to fail (e.g. bot not invited to channel, wrong channel name, etc.) and resolving those issues is cumbersome.
Acceptance Criteria
Add install command
- use Helm Go SDK underneath to install the chart
- Use Kubernetes API and stream Pod logs
- print them to user only errors/warnings/info
- ensure pretty print (logs are properly colored)
- make sure it can be run with debug/verbose
- support dry-run
- support Botkube version and overrides
- Respect KUBECONFIG env variable
Overview
A user needs to know whether the Botkube installation process is successful or not, and be informed of any errors. The current helm install process will time out if there are problems and the user needs to look at the pod logs to troubleshoot the issue. There are some common pitfalls with Botkube configuration that cause the installation to fail (e.g. bot not invited to channel, wrong channel name, etc.) and resolving those issues is cumbersome.
Acceptance Criteria
install
command- use Helm Go SDK underneath to install the chart
- Use Kubernetes API and stream Pod logs
- print them to user only errors/warnings/info
- ensure pretty print (logs are properly colored)
- make sure it can be run with debug/verbose
- support dry-run
- support Botkube version and overrides
- Respect KUBECONFIG env variable
New scope added
uninstall
command: Add botkube uninstall command #1141The text was updated successfully, but these errors were encountered: