datarobot-oss/datarobot-agent-skills / skills/datarobot-app-framework-cicd
datarobot-app-framework-cicd
FlaggedGuidance 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.
| File | Kind | Size |
|---|---|---|
| QUICK_REFERENCE.md | markdown | 4.0 KB |
| README.md | markdown | 6.6 KB |
| SKILL.md | skill md | 19.6 KB |
| examples/github-cd-pulumi-cloud.yml | config | 1.1 KB |
| examples/github-deploy-pulumi-cloud.yml | config | 1.3 KB |
| examples/github-destroy-pulumi-cloud.yml | config | 1.2 KB |
| examples/workflows-README.md | markdown | 3.0 KB |
| references/example-taskfile.yaml | config | 895 B |
| references/workflow-examples.md | markdown | 2.5 KB |
| scripts/decrypt-secrets.shexecutable | script | 1.2 KB |
| scripts/encrypt-secrets.shexecutable | script | 1.9 KB |
| scripts/github-cd.yml | config | 2.0 KB |
| scripts/github-deploy.yml | config | 5.0 KB |
| scripts/github-destroy.yml | config | 1.9 KB |
| scripts/gitlab-ci.yml | config | 4.7 KB |
| scripts/infra-README.md | markdown | 6.4 KB |
| scripts/pulumi-setup.shexecutable | script | 10.8 KB |
| scripts/setup-github-secrets.shexecutable | script | 3.6 KB |
| scripts/setup-gitlab-variables.shexecutable | script | 4.4 KB |
| scripts/taskfile-snippets.yaml | config | 5.6 KB |
scripts/setup-github-secrets.sh
View on GitHub#!/usr/bin/env bash
# Copyright (c) 2026 DataRobot, Inc. All rights reserved.
# SPDX-License-Identifier: Apache-2.0
# Add secrets to GitHub repository using GitHub CLI
# Requires: gh CLI (https://cli.github.com/)
set -euo pipefail
echo "π GitHub Secrets Setup"
echo "======================="
echo ""
# Check if gh is installed
if ! command -v gh &> /dev/null; then
echo "β GitHub CLI (gh) not installed"
echo ""
echo "Install with:"
echo " macOS: brew install gh"
echo " Linux: See https://github.com/cli/cli#installation"
echo ""
exit 1
fi
# Check if authenticated
if ! gh auth status &> /dev/null; then
echo "β Not authenticated with GitHub CLI"
echo "Run: gh auth login"
exit 1
fi
echo "β
GitHub CLI authenticated"
echo ""
# Get repository (or use current)
REPO=$(gh repo view --json nameWithOwner -q .nameWithOwner 2>/dev/null || echo "")
if [ -z "$REPO" ]; then
read -rp "Enter repository (owner/repo): " REPO
fi
echo "Repository: $REPO"
echo ""
# Function to add a secret (masked)
add_secret() {
local secret_name=$1
local secret_description=$2
local secret_value=""
echo "π Setting up secret: $secret_name"
echo " $secret_description"
read -rsp " Enter value: " secret_value
echo ""
if [ -n "$secret_value" ]; then
echo "$secret_value" | gh secret set "$secret_name" --repo "$REPO"
echo " β
Added $secret_name"
else
echo " βοΈ Skipped (empty value)"
fi
echo ""
}
# Function to add a plain (non-secret) Actions variable
add_variable() {
local var_name=$1
local var_description=$2
local default_value=${3:-}
local var_value=""
echo "π Setting up variable: $var_name"
echo " $var_description"
if [ -n "$default_value" ]; then
read -rp " Enter value [$default_value]: " var_value
var_value="${var_value:-$default_value}"
else
read -rp " Enter value: " var_value
fi
if [ -n "$var_value" ]; then
gh variable set "$var_name" --body "$var_value" --repo "$REPO"
echo " β
Set $var_name=$var_value"
else
echo " βοΈ Skipped (empty value)"
fi
echo ""
}
# Add secrets
echo "βββ Secrets (encrypted) ββββββββββββββββββββββββββββββββββββββββββββββββ"
echo "This setup requires ONE secret."
echo "All other credentials (DATAROBOT_API_TOKEN, PULUMI_ACCESS_TOKEN, LLM keys, etc.)"
echo "are stored encrypted in .env.gpg and loaded automatically by the workflow."
echo ""
add_secret "CICD_SECRET_PASSPHRASE" "GPG passphrase for decrypting .env.gpg"
# Add plain CI/CD variables (not sensitive β visible in logs)
echo "βββ Variables (plain text) βββββββββββββββββββββββββββββββββββββββββββββ"
echo "Pulumi stack names are not secrets β they are plain Actions variables."
echo ""
add_variable "PULUMI_STACK_CI_NAME" \
"Pulumi stack deployed on every merge to the default branch" \
"ci"
add_variable "PULUMI_STACK_REVIEW_NAME" \
"Pulumi stack name prefix for PR review apps (PR number appended automatically in the workflow)" \
"review"
echo ""
echo "π Secrets and variables setup complete!"
echo ""
echo "View all secrets: gh secret list --repo $REPO"
echo "View all variables: gh variable list --repo $REPO"
echo ""
echo "Next steps:"
echo "1. Ensure your .env.gpg is committed to the repository"
echo "2. Push your .github/workflows to trigger actions"
echo "3. Test with a pull request"
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| 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: 198k | Updated | Claude CodeCodex | Verified | Install |
| 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: 119k | Updated | Claude CodeCodex | Verified | Install |
| 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: 118k | Updated | Claude CodeCodex | Verified | Install |