Guides

Use Pad in CI

Provision Pads from CI pipelines and scripts.

CI pipelines often need a fresh Pad per build without committing a Padfile to every repo. The command takes the same fields as a Padfile, but as flags. It also accepts --padfile <path|-> when you'd rather generate or pipe TOML.

Authenticate

Generate an API key from your account, store it as a secret in your CI provider, and pass it via --api-key:

pad create --api-key "$PAD_API_KEY" --template myorg/node-20 ...

Every pad invocation accepts --api-key, so pad login and OS-keychain credentials are not needed in CI.

A typical pipeline

# .github/workflows/preview.yml
name: Preview Pad
on: [pull_request]

jobs:
  preview:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Install Pad CLI
        run: curl -fsSL https://pad.dev/install.sh | sh

      - name: Create Pad
        id: create
        env:
          PAD_API_KEY:

Use Pad in CI / Pad

Use Pad in CI

Authenticate

A typical pipeline

On this page

Wait or fire-and-forget

Bringing your own Padfile

See also