Skip to content

datarobot-oss/datarobot-agent-skills / skills/datarobot-app-framework-cicd

datarobot-app-framework-cicd

Flagged

Guidance for setting up CI/CD pipelines for DataRobot application templates using GitLab, GitHub Actions, and Pulumi for infrastructure as code. Use when setting up CI/CD pipelines, configuring deployments, or managing infrastructure for DataRobot application templates.

scripts/github-cd.yml

View on GitHub
---
# Example GitHub Actions continuous delivery workflow for DataRobot Application Templates
# Copy this to your repository as .github/workflows/cd.yml
#
# Triggers on every push to the default branch and deploys to the persistent CI stack.
# The stack name is controlled by the PULUMI_STACK_CI_NAME repository variable
# (set via: gh variable set PULUMI_STACK_CI_NAME --body 'ci').

name: Pulumi CD
on:
  push:
    branches:
      - main

# Restrict default permissions for all jobs — each job grants only what it needs.
permissions:
  contents: read

env:
  PULUMI_STACK: ${{ vars.PULUMI_STACK_CI_NAME || 'ci' }}

jobs:
  deploy:
    name: pulumi-deploy-ci-stack
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4

      - name: Decrypt Secrets
        run: |
          gpg --quiet --batch --yes --decrypt --passphrase="$CICD_SECRET_PASSPHRASE" --output .env .env.gpg
          # Load all .env variables into the GitHub Actions environment for subsequent steps
          grep -v '^#' .env | grep -v '^$' >> $GITHUB_ENV
        env:
          # Only this one secret needs to be stored in GitHub repository secrets
          CICD_SECRET_PASSPHRASE: ${{ secrets.CICD_SECRET_PASSPHRASE }}

      - uses: actions/setup-python@v5
        with:
          python-version: 3.12

      - name: Install Pulumi
        run: |
          curl -fsSL https://get.pulumi.com | sh
          echo "$HOME/.pulumi/bin" >> $GITHUB_PATH

      - name: Setup Project Dependencies
        run: |
          command -v uv >/dev/null 2>&1 || curl -LsSf https://astral.sh/uv/install.sh | sh
          uv venv .venv
          source .venv/bin/activate
          uv pip install -r requirements.txt

      - name: Deploy CI Stack
        run: |
          source .venv/bin/activate
          export $(grep -v '^#' .env | xargs)
          # PULUMI_STACK selects the persistent CI stack; --create initialises it if it doesn't exist yet
          pulumi stack select --create $PULUMI_STACK
          pulumi up --yes
          echo "✅ Deployed CI stack: $PULUMI_STACK"
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 322kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall