Skip to content

Deployment

Deployments are handled via GitHub Actions, using shared reusable workflows from subscribed-aps/workflows.

Triggering a Deploy

Deployments are triggered manually via workflow_dispatch in the GitHub Actions UI:

  1. Go to ActionsDeploy Bedrock
  2. Click Run workflow
  3. Select the target environment: develop or master
  4. Click Run workflow

The workflow calls the shared reusable workflow at subscribed-aps/workflows/.github/workflows/deploy-bedrock.yml@main.

Environments

Branch Environment Notes
develop Staging Deployed on demand
master Production Deployed on demand

Workflow File

.github/workflows/deploy-bedrock.yml:

name: Deploy Bedrock

on:
  workflow_dispatch:
    inputs:
      environment:
        description: "Deployment environment"
        required: true
        type: choice
        options:
          - develop
          - master

jobs:
  deploy:
    uses: subscribed-aps/workflows/.github/workflows/deploy-bedrock.yml@main
    with:
      environment: ${{ inputs.environment }}
    secrets: inherit

Required Secrets

The following secrets must be configured in the GitHub repository settings (inherited by the reusable workflow):

Secret Description
DOTENV_KEY Key to decrypt .env.vault at deploy time
HANDBOOK_DISPATCH_TOKEN Token for notifying the Engineering Handbook on docs changes

Check subscribed-aps/workflows for any additional secrets required by the shared workflow.

Engineering Handbook Notifications

Documentation changes pushed to master automatically notify the Engineering Handbook via .github/workflows/notify-handbook.yml. This triggers whenever files in docs/ are updated.