codestudio
Use when setting up a new Code Studio (GitLab CI/CD) project, changing PHP version in Code Studio builds. NOT for checking pipeline job status — use pipelines-cli-pipeline-operations for that.
Works with
--- name: codestudio description: Use when setting up a new Code Studio (GitLab CI/CD) project, changing PHP version in Code Studio builds. NOT for checking pipeline job status — use pipelines-cli-pipeline-operations for that. license: MIT --- # Code Studio with Acquia CLI Use when: - Setting up a new Code Studio project for a Cloud application - Changing the PHP version used in Code Studio builds - Migrating an existing `acquia-pipelines.yml` to a `.gitlab-ci.yml` file > **Note:** This skill covers Code Studio *setup* only. To trigger builds, check job status, or stream logs, use **pipelines-cli** (`pipelines-cli-pipeline-operations`). Code Studio is Acquia's GitLab-based CI/CD platform. It runs build pipelines, automated tests, and deployments for your Cloud Platform applications. --- ## Set Up Code Studio (Wizard) The wizard creates and configures a Code Studio project for your application: ```bash acli codestudio:wizard ``` Alias: `acli cs:wizard` The wizard will: 1. Authenticate with your Cloud Platform application 2. Connect to your GitLab instance 3. Create or configure a Code Studio project 4. Set up CI/CD variables **Non-interactive (provide all credentials upfront):** ```bash acli codestudio:wizard \ --key="$ACQUIA_KEY" \ --secret="$ACQUIA_SECRET" \ --gitlab-token="$GITLAB_TOKEN" \ --gitlab-project-id=12345 \ --gitlab-host-name=code.acquia.com ``` > **Security:** Never pass credential values directly in the command line — they appear in shell history and process listings. Always source them from environment variables or a secrets manager. Options: | Option | Description | |---|---| | `--key` | Cloud Platform API key for Code Studio to use | | `--secret` | Cloud Platform API secret for Code Studio to use | | `--gitlab-token` | GitLab personal access token | | `--gitlab-project-id` | Integer project ID of the GitLab project to configure | | `--gitlab-host-name` | GitLab hostname (defaults to Acquia's instance) | --- ## Change PHP Version in Code Studio Update the PHP version used in Code Studio build containers: ```bash acli codestudio:php-version <version> ``` Example: ```bash acli codestudio:php-version 8.2 acli codestudio:php-version 8.3 ``` ## Typical Workflow: Onboard to Code Studio ```bash # Step 1: Set up Code Studio project acli codestudio:wizard # Step 2: Set PHP version if needed acli codestudio:php-version 8.2 ``` --- ## Best Practices 1. **Run the wizard first** — It sets up all required CI/CD variables automatically. 2. **Use environment variables for credentials in CI** — Pass `--key`, `--secret`, and `--gitlab-token` via environment variables (e.g., `--key="$ACQUIA_KEY"`), never as literal values. Store secrets in your CI/CD platform's secret store. 3. **Match PHP versions** — Ensure `codestudio:php-version` matches the version in your `composer.json` platform requirements. --- ## Troubleshooting ### "GitLab project not found" Verify the project ID and that your token has access: ```bash # Re-run wizard interactively to select the right project acli codestudio:wizard ``` ### Authentication errors Ensure your Cloud API key/secret are valid: ```bash acli auth:login acli auth:me ``` --- ## Related Topics - **[Getting Started](../getting-started/SKILL.md)** — Authentication setup - **[Environment Management](../environment-management/SKILL.md)** — Deploy to environments - **[Pull & Push](../pull-push/SKILL.md)** — Push build artifacts
More Deployment & CI/CD skills
azure-enterprise-infra-planner
microsoft/azure-skills
Architect and provision enterprise Azure infrastructure from workload descriptions. For cloud architects and platform engineers planning networking, identity, security, compliance, and multi-resource topologies with WAF alignment. Generates Bicep or Terraform directly (no azd). WHEN: 'plan Azure infrastructure', 'architect Azure landing zone', 'design hub-spoke network', 'plan multi-region DR topology', 'set up VNets firewalls and private endpoints', 'subscription-scope Bicep deployment', 'Azure Backup for VM workloads'. PREFER azure-prepare FOR app-centric workflows.
azure-kubernetes-app-deploy
microsoft/azure-skills
Use when deploying an existing web application or API to an already-running Azure Kubernetes Service cluster. Detects the framework, generates a Dockerfile and Kubernetes manifests, validates against AKS Deployment Safeguards, and deploys with verification. WHEN: deploy app to AKS, deploy to existing AKS cluster, containerize app for Kubernetes, generate K8s manifests for Azure, set up CI/CD for AKS, my AKS deployment is failing safeguard checks, I have a Django/Express/Spring Boot app to run on AKS. DO NOT USE FOR: creating or provisioning an AKS cluster (use azure-kubernetes), assessing migration to AKS Automatic (use azure-kubernetes-automatic-readiness), or deploying to non-AKS targets like Web Apps, Container Apps, or Functions.
finetuning
microsoft/azure-skills
Fine-tune models on Microsoft Foundry using SFT (supervised), DPO (preference), or RFT (reinforcement with graders). Covers dataset preparation, training job submission, deployment, and evaluation. USE FOR: fine-tune, SFT, DPO, RFT, training data, grader, distillation, fine-tuned model, training job, large file upload, calibrate grader, deploy fine-tuned model, evaluate fine-tuned model. DO NOT USE FOR: general model deployment without fine-tuning (use deploy-model), agent creation (use agents), prompt optimization without training (use prompt-optimizer).

