Update an existing rota

PATCH /rotas/:id

• name - string, optional
• description - string, optional
• assigned - string, optional

Add users to a rota

POST    /rotas/:id/users

• users - array of strings, required

Add an endpoint to delete a user from a rota

DELETE  /rotas/:rotaName/users/:userName

Delete an existing rota

DELETE /rotas/:id

In order to test changes without breaking things in production, I would like to have a separate staging environment for the rota api

Requirements

• Set up a staging database in supabase
• Create a new application on fly.io for the staging application, with the necessary secrets to point to the new supabase database
• Split the fly.toml configuration into 2 files (fly.production.toml and fly.staging.toml) pointing the latter to the new application
• Update Makefile with commands to deploy to each environment

e.g.

fly deploy --config fly.staging.toml

Resources

• Staging vs production environnement with the same code base - General - Fly.io

Requirements

Add two GitHub action workflows

• staging.yml - triggered when changes are merged to develop
• production.yml - triggered when changes are merged to main

For each:

• Deploy database migrations to supabase
• Deploy application to fly.io
• Should be idempotent, allowing them to be re-run safely

Resources

• Managing Environments | Supabase Docs
• Database migrations explained with Supabase — Restack

Add a new database table to store Slack installations and tokens for OAuth authentication

Resources

• Authenticating with OAuth - Slack | Bolt for JavaScript
• Database | Supabase Docs
• Understanding API Keys | Supabase Docs
• Slack API: Applications | Russell Slack

Example

{
  team: { id: 'T012345678', name: 'example-team-name' },
  enterprise: undefined,
  user: { token: undefined, scopes: undefined, id: 'U01234567' },
  tokenType: 'bot',
  isEnterpriseInstall: false,
  appId: 'A01234567',
  authVersion: 'v2',
  bot: {
    scopes: [
      'chat:write',
    ],
    token: 'xoxb-244493-28*********-********************',
    userId: 'U012345678',
    id: 'B01234567'
  }
}

Tables

slack_installations

slack_bots

slack_bot_scopes

The table definition in markdown format with PostgreSQL data types would be:

slack_teams

slack_users

slack_user_scopes

Insert a new rota

POST /rotas/

• name - string, required
• description - string, optional

App: rota-api

This is the feature branch for several issues related to authentication