Define TTL for sensitive messages sent by Botkube

[mszostok]

Overview

Botkube sends messages to communication platforms that may contain sensitive data. For example, logs, K8s secrets, etc. Such messages cannot be easily deleted unless you have proper permissions.

To mitigate such problem, we can provide an option to define TTL for such messages. A given message can be deleted or replaced with a placeholder message informing why a given message was removed.

Acceptance Criteria

• provide an option to associate a given TTL with a given message
  • for example, based on executed command prefix (kc logs = 1h TTL)
  • for example, based on message content - as we sent also a command header, matching against command would be also possible and at the same time it will be more generic.
• make sure that Bot has proper permission to delete own messages
  • in case of Slack we don't need to do anything as we have already chat:write perm and based on docs: When used with a bot token, this method may delete only messages posted by that bot.
• make sure that messages sent in thread are also deleted
• update documentation
• provide e2e tests

[mszostok]

This was a user request from our Slack: