Deployment

Agents deploy to Connic Cloud through automatic Git-based deployments or the CLI, with deployment tests, build logs, and activation of successful deployments.

Overview

Connic supports two deployment methods for different workflows:

Git Integration

Connect a Git repository for automatic deployments on push. Connic supports GitHub, GitLab, and Bitbucket.

1. 1

   Connect a Repository

   1. 1

      Go to Project Settings → Git & Environments

   2. 2

      Click Connect and select a provider (GitHub, GitLab, or Bitbucket)

   3. 3

      Authorize Connic to access the repositories. GitLab.com uses OAuth; for Self-Managed GitLab 15.5 or later, first add the instance under Account → Git Accounts with a personal access token that has the api scope. The GitLab user must be an administrator or have the Maintainer or Owner role on each repository.

   4. 4

      Select the repository containing the agents/ directory and any supporting project directories

   5. 5

      For a monorepo, set the Repository root directory to the path containing the Connic SDK project (e.g. services/agents). Leave empty when the SDK files are at the repo root.

   6. 6

      Connic installs a webhook on the repository to detect pushes and pull or merge requests

2. 2

   Configure Environment Branches

   1. 1

      Open Project Settings → Git & Environments

   2. 2

      For each environment, set the Git Branch that triggers deployments

   3. 3

      Pushes to branches that are not mapped to any environment are ignored

   For example:

   • • Production → main
   • • Staging → develop
   • • Development → feature/customer-import (optional)
3. 3

   Push to Deploy

   Push to the configured branch. Connic detects the push via webhooks and creates a deployment.

   terminal

   Copy

   # Push to trigger deployment
   git add .
   git commit -m "Update agents"
   git push origin main

CLI Deployments

Use the CLI to deploy from a local machine or CI/CD pipeline when:

• The project has no Git repository connected in Connic
• The deployment starts from a local checkout or CI/CD pipeline
• The source repository uses any Git provider or no provider

1. 1

   Install the SDK

   terminal

   Copy

   pip install connic-composer-sdk

2. 2

   Authenticate

   Run the login command. It opens the dashboard to create an API key, then prompts for the resulting login token:

   terminal

   Copy

   connic login

   This creates a .connic file:

   .connic

   Copy

   {
     "api_key": "cnc_xxxxxxxxxxxx",
     "project_id": "your-project-uuid"
   }

   For CI/CD, use environment variables instead: CONNIC_API_KEY and CONNIC_PROJECT_ID

3. 3

   Choose the Environment

   Run connic deploy --list to see the available targets. Environment names are the primary selector; --env also accepts an environment ID.

4. 4

   Deploy

   terminal

   Copy

   # Choose an environment by name and confirm
   connic deploy
   
   # List available deployment targets
   connic deploy --list
   
   # Select a target directly, then confirm
   connic deploy --env staging

   Without flags, the CLI lists environments by name. Select a target, review the deployment summary, and confirm before the CLI uploads files.

   The CLI uploads supported files from agents/, tools/, middleware/, schemas/, guardrails/, hooks/, and tests/, plus requirements.txt. Nested files are included.

CI/CD Integration

Use the CLI in a CI/CD pipeline when the Connic project has no connected Git repository. The source repository can use any provider. For unattended deployments, pass an explicit --env and --yes.

name: Deploy to Connic
on:
  push:
    branches: [main]
jobs:
  deploy:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: pip install connic-composer-sdk
      - run: connic deploy --env "$CONNIC_ENV_NAME" --yes
        env:
          CONNIC_API_KEY: ${{ secrets.CONNIC_API_KEY }}
          CONNIC_PROJECT_ID: ${{ secrets.CONNIC_PROJECT_ID }}
          CONNIC_ENV_NAME: ${{ secrets.CONNIC_ENV_NAME }}

deploy:
  stage: deploy
  script:
    - pip install connic-composer-sdk
    - connic deploy --env "$CONNIC_ENV_NAME" --yes
  variables:
    CONNIC_API_KEY: $CONNIC_API_KEY
    CONNIC_PROJECT_ID: $CONNIC_PROJECT_ID

Set CONNIC_API_KEY, CONNIC_PROJECT_ID, and CONNIC_ENV_NAME as CI/CD secrets in the provider settings.

What Happens During Deployment

A deployment stopped by the source review is marked Blocked. Connic does not build, test, or activate it. Open the deployment to see instructions for contacting support.

Monitoring Deployments

View deployment status and logs in the Deployments tab:

• See all deployments with status and duration
• Click a deployment to view build logs
• The currently serving deployment is marked "Active"

Rollback a Deployment

Activate another successful deployment from the Deployments tab:

1. 1

   Open the Deployments tab and select a successful deployment

2. 2

   Click the Activate button on that deployment

3. 3

   Traffic is routed to the selected deployment without rebuilding it

When a Deployment Fails

When a build fails, the deployment is marked Failed and the active deployment continues serving traffic.