Improve Slack app development experience by leveraging self-managed support

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Problem

The current method (doc) of a developer setting up an environment to develop the GitLab for Slack app is limited:

• It involves several manual configuration steps each time we stand up a GitPod instance.
• We can only truly have one developer work on it at a time, because certain configuration URLs (like for the Slack events API) only allows us to specify a single URL, which must be one developer's GitPod instance.

Solution

Leverage the support for self-managed GitLab for Slack app #358872 (closed) flow for developers.

Proposal

After #358872 (closed), developers could also create single (disposable) Slack apps using their GitPod instance using the same method, which would be fully configured for their instance.

These would be installed into our Slack testing workspace.

This would:

• Mean very low configuration overhead.
• Developers could develop at the same time, as they will be using separate apps.

The one clash between multiple development Slack apps would be slash commands - we would need to add a small amount of logic for Rails.development? where the slash command configured was unique. 🤔 Or even better, make the slash command configurable in the admin - this might be a feature that SM customers might appreciate if they want to use the GitLab for Slack app slash commands for more than one GitLab instance.

We would end up with a ton of these singleton apps in our test workspace if we don’t clean up after ourselves when we’re done - but we can work that last bit out. The simple way would be to document that we remove them from our workspace when we're done. Otherwise, there may be ways of auto-removing them with Slack APIs.