Put tenant-isolation evidence directly in the pull request.

Add one pull-request job

Pin a released BoundaryCI version or exact commit in production. The scanner requires no database secret for deterministic migration analysis.

name: Tenant isolation
on: [pull_request]

jobs:
  boundaryci:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v7
      - uses: sir-gig/boundaryci@v0.4.0
        with:
          target: .
          fail-on: high

Annotate the vulnerable migration

New deterministic findings appear as workflow annotations with rule ID, severity, evidence, and remediation. Baseline and actively waived findings remain visible in reports without creating new merge noise.

Make the job a required check

After the workflow has completed successfully once, require its job in the repository's main-branch rules. A pull request that introduces a new finding at or above the configured threshold will then be unable to merge.

Store the token as a GitHub secret

BoundaryCI Cloud shows a repository-bound token once. In the GitHub repository, open Settings, then Secrets and variables, then Actions. Create a repository secret named BOUNDARYCI_CLOUD_TOKEN and paste the token as its value. The token never belongs in the workflow file.

Reference the secret from the workflow

The repository dashboard keeps a copyable setup guide after onboarding. Its YAML enables minimized Cloud history and contains only a GitHub secret reference, so it is safe to commit. If the token is replaced later, update the GitHub secret value without changing the workflow.

          managed-fireworks: "true"
          upload: "true"
          cloud-url: YOUR_BOUNDARYCI_INGEST_URL
          cloud-token: ${{ secrets.BOUNDARYCI_CLOUD_TOKEN }}

Authorize managed AI without another GitHub secret

Team, Growth, and Enterprise organization managers can accept the managed-AI disclosure in the BoundaryCI dashboard. After consent, the existing repository token requests Fireworks semantic review automatically; the Fireworks API key remains inside BoundaryCI's server environment and never enters GitHub.

Each repository starts enabled after organization consent. Disable it from the repository setting or set managed-fireworks to false in the workflow to keep that repository deterministic-only.