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 |
examples/workflows-README.md
View on GitHub# CI/CD Setup
This directory contains GitHub Actions workflows for deploying to DataRobot using Pulumi Cloud.
## Workflows
| File | Trigger | What it does |
|------|---------|--------------|
| `cd.yml` | Automatic — every merge to `main` | Deploys `main` to the persistent CI stack |
| `deploy-pr.yml` | Manual — you choose branch and stack name | Deploys a preview stack from a PR branch |
| `destroy.yml` | Manual — you enter the stack name | Destroys a named Pulumi stack |
`cd.yml` is the only workflow that runs automatically. Everything else requires you to trigger it from the Actions tab.
## One-time setup
### 1. Create a Pulumi Cloud account
Sign up at [app.pulumi.com](https://app.pulumi.com) (free tier is sufficient for most projects).
Create an access token: click your **profile icon → Access Tokens → Create token**. Copy the token — you will need it in step 3.
### 2. Get a DataRobot API key
Ask your DataRobot admin to create a **service account** user (e.g. `ci-bot@your-org.com`) and generate an API key under **Developer Tools → API Key**. Using a service account instead of a personal API key prevents CI/CD from breaking when people leave the team.
> If you are just getting started, you can use your own personal API key temporarily and replace it later.
### 3. Add GitHub Secrets
Go to: **Settings → Secrets and variables → Actions → Secrets tab → New repository secret**
| Secret name | Where to get it |
|-------------|----------------|
| `DATAROBOT_API_TOKEN` | DataRobot → Developer Tools → API Key |
| `PULUMI_ACCESS_TOKEN` | Pulumi Cloud → Profile → Access Tokens |
Both secrets are required. The workflows will not run without them.
### 4. (Optional) Set a custom CI stack name
The `cd.yml` workflow deploys to a Pulumi stack named `ci` by default. To use a different name, add a repository variable:
**Settings → Secrets and variables → Actions → Variables tab → New repository variable**
| Variable name | Value |
|---------------|-------|
| `PULUMI_STACK_CI_NAME` | Your preferred stack name (e.g. `ci`, `prod`, `staging`) |
Skip this step if `ci` is fine.
## How to trigger deployments
**Automatic deploy (merge to main):**
`cd.yml` runs automatically every time code is merged to `main`. No action needed.
**Manual PR preview deploy:**
1. Open a PR and get ready to test it in a live environment.
2. Go to **Actions → Deploy (PR Preview)** in the GitHub UI.
3. Click **Run workflow**.
4. Select your PR branch from the dropdown.
5. Enter a stack name — tip: use the PR number (e.g. `pr-42`) so it's easy to track.
6. Click **Run workflow**. Each stack is isolated, so multiple PRs can have their own live environment.
**Destroy a stack (manual cleanup):**
1. Go to **Actions → Destroy Stack**.
2. Click **Run workflow → Run workflow**.
3. Enter the exact stack name you want to destroy (e.g. `pr-42` or `ci`).
> The CI stack (`ci`) is recreated automatically on the next merge to `main`. Destroy it only if you want to tear everything down.
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 |