Slack token from helm chart is out of sync with code

[leovalverde-practiv]

Issue description

The latest version of the helm chart (v1.0.5) feeds the SLACK_TOKEN secret (via Kubernetes secrets) into the application container, but the codebase expects it provided as SLACK_BOT_TOKEN.

Temporary fix

There is a workaround, which is to set secret.create="false" on the helm chart, and then provide your own secret containing a value for SLACK_BOT_TOKEN, also setting your custom secret name (e.g. "keel") as secret.name="keel", but that's not good and should be fixed.

Note: Missing info on docs

As a side note, the documentation seems to be quite behind compared to the codebase, requiring developers to explore the codebase in order to customise the application's behaviour or solve issues. Some examples are:

• Authentication via Google Workload Identity is now implemented, but there are no mentions to it on the documentation.
• When using slack for notifications, granting the scope chat:write.customize allows us to customise the username for slack messages via the helm parameter slack.botName. The docs don't mention anything about slack scopes.