Manage redirects as code: Terraform, CI and infrastructure as code

Why manage redirects as code#

• Every change is reviewed in a pull request and has a history in git.
• Redirects ship with the site change that needs them, from the same pipeline.
• The same file can recreate a workspace's redirects, for example for a staging domain.

Today: a redirects file and the API#

1. Keep redirects.csv in your repository with the columns source_url, destination and type, the same format as the CSV import.
2. Store an API token as a CI secret (REDIRHUB_TOKEN). Each token is scoped to one workspace.
3. On merge, run a script that creates the rows that don't exist yet with POST /links and updates the ones whose destination changed with PUT /links/{id}. The script in Create, update and delete redirects in bulk with the API is a starting point.

yaml# .github/workflows/redirects.yml
name: Apply redirects
on:
  push:
    branches: [main]
    paths: [redirects.csv]
jobs:
  apply:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: pip install requests
      - run: python scripts/apply_redirects.py redirects.csv
        env:
          REDIRHUB_TOKEN: ${{ secrets.REDIRHUB_TOKEN }}

To see what a change would do before it runs, preview bulk updates with POST /bulk/summary, which returns the matched links and the first before-and-after destinations without writing anything.

Terraform provider (coming soon)#

A RedirHub provider for Terraform and OpenTofu is coming soon, so domains and redirects can be declared as resources next to your DNS and CDN, with plan and apply like the rest of your stack. Early access is available now on request and can be ready for your workspace in as little as 3 days.

To request early access, use the contact form or email success@redirhub.com with your workspace name, the tool you use (Terraform or OpenTofu) and roughly how many domains and redirects you manage.