jeremylongshore/tons-of-skills-marketplace / plugins/devops/deployment-pipeline-orchestrator/skills/orchestrating-deployment-pipelines
orchestrating-deployment-pipelines
VerifiedDeploy use when you need to work with deployment and CI/CD. This skill provides deployment automation and orchestration with comprehensive guidance and automation. Trigger with phrases like "deploy application", "create pipeline", or "automate deployment".
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 4.3 KB |
| assets/README.md | markdown | 491 B |
| assets/example_config.yaml | config | 4.1 KB |
| assets/pipeline_template.yaml | config | 2.6 KB |
| references/README.md | markdown | 75 B |
| scripts/README.md | markdown | 637 B |
| scripts/init_pipeline.pyexecutable | script | 2.7 KB |
assets/example_config.yaml
View on GitHub# example_config.yaml
# Configuration file for the Deployment Pipeline Orchestrator plugin.
# General pipeline settings
pipeline_name: "Example Application Deployment" # Name of this deployment pipeline
application_name: "ExampleApp" # Name of the application being deployed
environment: "production" # Target environment (e.g., staging, production, development)
# Source code repository settings
repository:
type: "git" # Type of repository (e.g., git, svn)
url: "https://github.com/YOUR_GITHUB_USERNAME/ExampleApp.git" # URL of the repository
branch: "main" # Branch to deploy from
credentials:
username: "YOUR_GITHUB_USERNAME" # Username for accessing the repository (if required)
password: "YOUR_GITHUB_PASSWORD" # Password or token for accessing the repository (if required, consider using secrets management)
# Build stage configuration
build:
enabled: true # Whether to enable the build stage
builder: "docker" # Build tool to use (e.g., docker, maven, gradle)
dockerfile_path: "Dockerfile" # Path to the Dockerfile (if using Docker)
context_path: "." # Build context path
image_name: "example-app" # Name of the Docker image to build
image_tag: "latest" # Tag for the Docker image
registry: # Docker registry settings (optional)
url: "docker.io" # URL of the Docker registry
username: "YOUR_DOCKER_USERNAME" # Username for accessing the registry
password: "YOUR_DOCKER_PASSWORD" # Password or token for accessing the registry (if required, consider using secrets management)
build_args: # Additional build arguments (optional)
- "VERSION=1.0.0"
# Test stage configuration
test:
enabled: true # Whether to enable the test stage
test_runner: "pytest" # Testing framework (e.g., pytest, unittest)
test_command: "pytest tests/" # Command to run the tests
dependencies: # Dependencies required for testing (optional)
- "pytest"
- "requests"
# Deploy stage configuration
deploy:
enabled: true # Whether to enable the deploy stage
deployment_platform: "kubernetes" # Platform to deploy to (e.g., kubernetes, aws, azure)
kubernetes: # Kubernetes deployment settings (required if deployment_platform is kubernetes)
namespace: "example-app-ns" # Kubernetes namespace
deployment_file: "k8s/deployment.yaml" # Path to the Kubernetes deployment file
service_file: "k8s/service.yaml" # Path to the Kubernetes service file
ingress_file: "k8s/ingress.yaml" # Path to the Kubernetes ingress file (optional)
image_pull_secret: "docker-registry-secret" # Name of the image pull secret (optional)
aws: # AWS deployment settings (required if deployment_platform is aws)
region: "us-east-1" # AWS region
ecr_repository: "YOUR_ECR_REPOSITORY_NAME" # Name of the ECR repository
ecs_cluster: "YOUR_ECS_CLUSTER_NAME" # Name of the ECS cluster
azure: # Azure deployment settings (required if deployment_platform is azure)
resource_group: "YOUR_RESOURCE_GROUP_NAME" # Name of the Azure resource group
container_registry: "YOUR_CONTAINER_REGISTRY_NAME" # Name of the Azure container registry
# Monitoring stage configuration
monitor:
enabled: true # Whether to enable the monitor stage
monitoring_tool: "prometheus" # Monitoring tool to use (e.g., prometheus, datadog)
endpoints: # Endpoints to monitor
- "http://localhost:8080/health"
alerts: # Alerting configuration
cpu_usage: # Example alert for CPU usage
threshold: 80 # Percentage threshold
severity: "critical" # Severity of the alert
memory_usage: # Example alert for memory usage
threshold: 90 # Percentage threshold
severity: "warning" # Severity of the alert
# Notification settings
notifications:
enabled: true # Whether to enable notifications
type: "slack" # Notification type (e.g., slack, email)
slack: # Slack notification settings (required if type is slack)
webhook_url: "example-value" # Slack webhook URL
email: # Email notification settings (required if type is email)
sender: "deployments@example.com" # Sender email address
recipients: # List of recipient email addresses
- "admin@example.com"
- "devops@example.com"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: 323k | 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 |