Persist sent help messages

[mszostok]

Description

Changes proposed in this pull request:

• Persist sent help messages

Testing

I wanted to add the e2e tests but I would impact the future improvements with parallel test. I cannot modify the BotKube configuration and delete the pod.

Manual testing:

1. Checkout this branch: gh pr checkout 738
2. Create cluster: k3d cluster create
3. Install BotKube with Slack:

   # /tmp/slack.yaml
   communications:
     default-group:
       slack:
         channels:
           default:
             name: random
         enabled: true
         appToken: "xapp-1-"
         botToken: "xoxb-"
   
   image:
     repository: kubeshop/pr/botkube
     pullPolicy: Always
     tag: 738-PR
   
   analytics:
     disable: true
   

   helm upgrade botkube --install --namespace botkube ./helm/botkube --create-namespace -f /tmp/slack.yaml
   

4. See the help message on the #random channel.
5. Delete the Pod (simulate restart): kubectl -n botkube delete po -l app=botkube --force
6. Help message should NOT be reposted on #random channel
7. Upgrade BotKube with Discord:

   # /tmp/discord.yaml
   communications:
     default-group:
       discord:
         enabled: true
         channels:
           default:
             id: ""
         botID: ""
         token: ""
   
   image:
     repository: kubeshop/pr/botkube
     pullPolicy: Always
     tag: 738-PR
   
   analytics:
     disable: true

   helm upgrade botkube --install --namespace botkube ./helm/botkube --create-namespace -f /tmp/discord.yaml
   

8. Restart Pod: kubectl delete po -l app=botkube --force
9. New help message should be visible on Discord channel

Related issue(s)

• Show interactive help command to the user #683

[ezodude]

5. Delete the Pod (simulate restart): kubectl -n botkube delete po -l app=botkube --force
6. Help message should be reposted on #random channel

So far only checked the code, but a question regarding steps 5 & 6 ... my assumption is:

• Deleting the Pod would NOT re-post the help message on Slack.
• The BotKube system ConfigMap would continue to exist across Pod restarts.

... Or did I get this wrong?

(about to run BotKube locally)

[ezodude]

👍 ...

Acceptance criteria 5 & 6 should be updated to:
5. Delete the Pod (simulate restart): kubectl -n botkube delete po -l app=botkube --force
6. Help message should NOT be reposted on #random channel

Successfully tested locally with Slack & Discord.

[mszostok]

@ezodude yes, you are right about the 6th point, sorry for confusion 👍