CI/CD Integration

This page describes common patterns for automating policy deployment.

Recommended Pattern

• Keep policies in version control.
• Validate in CI.
• Deploy via API/CLI with least-privilege credentials.

Secrets

Do not commit credentials.

• Use your CI secret store (for example GitHub Actions Secrets) for API keys.
• Prefer short-lived credentials where available.

Example (GitHub Actions)

name: Deploy Aegis Policies
on:
  push:
    branches: [ main ]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - name: Deploy policies
        env:
          VELIKEY_API_KEY: ${{ secrets.VELIKEY_API_KEY }}
        run: |
          # Replace with your chosen deployment mechanism (API/CLI).
          echo "Deploying policies..."