Configuration

AeroDeploy’s configuration system uses declarative YAML definitions, allowing your release engineering team to version control your entire CI/CD lifecycle using GitOps best practices.

The aero.yaml Manifest

Every repository orchestrated by AeroDeploy requires an aero.yaml file in its root directory. This manifest defines your build, test, and deploy stages.

version: '2.0'
project:
  name: "global-payment-gateway"
  tier: "tier-1-critical"

stages:
  - name: build
    runner: ubuntu-latest
    steps:
      - uses: aerodeploy/setup-node@v2
      - run: npm ci
      - run: npm run build

  - name: security-scan
    runner: sec-agent-pool
    steps:
      - uses: aerodeploy/sast-scan@v3
        with:
          strict_mode: true

  - name: deploy-prod
    needs: [build, security-scan]
    environment: production
    strategy: blue-green
    steps:
      - run: aero rollout start

Environment Variables and Secrets

AeroDeploy seamlessly integrates with enterprise secret managers like HashiCorp Vault, AWS Secrets Manager, and Azure Key Vault.

Define secrets in your aero.yaml by referencing the secret paths:

env:
  DATABASE_URL: ${{ secrets.PROD_DB_URL }}
  API_KEY: ${{ secrets.STRIPE_API_KEY }}

Role-Based Access Control (RBAC)

To enforce compliance, AeroDeploy provides robust RBAC. Map your identity provider (Active Directory, Okta, etc.) groups to AeroDeploy roles:

• Pipeline Admin: Full access to edit pipelines and secrets.
• Deployer: Can trigger manual approvals for production deployments.
• Viewer: Read-only access to deployment logs.

Configure these mappings in your AeroDeploy Administration Dashboard under Settings > IAM.