CI Integration

GitLab CI

stages:
    - build
    - deploy

build:
    stage: build
    image: docker:latest
    services:
        - docker:dind
    script:
        - docker build -t my-app:$CI_COMMIT_SHA .
        - docker push my-app:$CI_COMMIT_SHA

deploy:
    stage: deploy
    image: ghcr.io/zyno-io/dag/cli:latest
    script:
        - dag-deploy ./chart
          --server https://dag.example.com
          --deploy-version $CI_COMMIT_SHA
          --set image.tag=$CI_COMMIT_SHA

In GitLab CI, dag-deploy auto-detects:

• Repo URL from CI_PROJECT_URL
• Job ID from CI_JOB_ID
• Job Token from CI_JOB_TOKEN

No additional configuration is needed.

Same-Branch Promotion

When multiple DAG environments use the same source branch, pass the target environment name from each CI job. For example, a production job can require manual approval and then deploy the same main commit:

stages:
    - deploy
    - promote

deploy-staging:
    stage: deploy
    image: ghcr.io/zyno-io/dag/cli:latest
    script:
        - dag-deploy ./chart
          --server https://dag.example.com
          --environment staging
          --deploy-version $CI_COMMIT_SHA

deploy-production:
    stage: promote
    image: ghcr.io/zyno-io/dag/cli:latest
    needs: [deploy-staging]
    when: manual
    script:
        - dag-deploy ./chart
          --server https://dag.example.com
          --environment production
          --deploy-version $CI_COMMIT_SHA

GitHub Actions

WARNING

GitHub Actions support is planned but not yet implemented on the server side. Job token verification for GitHub will fail at runtime until this is completed.

name: Deploy

on:
    push:
        branches: [main]

jobs:
    deploy:
        runs-on: ubuntu-latest
        container:
            image: ghcr.io/zyno-io/dag/cli:latest
        steps:
            - uses: actions/checkout@v4

            - name: Deploy
              run: |
                  dag-deploy ./chart \
                    --server https://dag.example.com \
                    --deploy-version ${{ github.sha }} \
                    --set image.tag=${{ github.sha }}
              env:
                  GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

The CLI auto-detects:

• Repo URL from GITHUB_SERVER_URL and GITHUB_REPOSITORY
• Job ID from GITHUB_RUN_ID
• Job Token from GITHUB_TOKEN or ACTIONS_RUNTIME_TOKEN

Fetching Deployed Chart & Values

You can retrieve the currently deployed chart or values from the IaC repository in any CI job. This is useful for comparing changes, extracting configuration, or building on top of the current deployment state.

Downloading the Chart

# GitLab CI
fetch-chart:
    stage: prepare
    image: ghcr.io/zyno-io/dag/cli:latest
    script:
        - dag-get-chart ./deployed-chart.tgz
          --server https://dag.example.com
    artifacts:
        paths:
            - deployed-chart.tgz

Fetching Values as JSON

# GitLab CI
fetch-values:
    stage: prepare
    image: ghcr.io/zyno-io/dag/cli:latest
    script:
        - dag-get-values --server https://dag.example.com > current-values.json
    artifacts:
        paths:
            - current-values.json

Both dag-get-chart and dag-get-values use the same CI auto-detection as dag-deploy — no extra credentials are needed.

Environment Variables

Instead of CLI flags, you can set environment variables. This is useful for configuring DAG once in your CI project settings:

Variable	Description
DAG_SERVER_URL	DAG server URL
DAG_REPO_URL	Override auto-detected repo URL
DAG_JOB_ID	Override auto-detected job ID
DAG_JOB_TOKEN	Override auto-detected job token
DAG_ENVIRONMENT	Target environment name when a branch has multiple environments
DAG_DEPLOY_VERSION	Deployment version
DAG_TIMEOUT	Deprecated; accepted and ignored

Using the Docker Image

The ghcr.io/zyno-io/dag/cli image contains dag-deploy, dag-get-chart, and dag-get-values. Use it as your CI job image:

# GitLab CI
deploy:
    image: ghcr.io/zyno-io/dag/cli:latest

# GitHub Actions
jobs:
    deploy:
        container:
            image: ghcr.io/zyno-io/dag/cli:latest