Generate Promotion Workflow Skill

Overview

The Generate Promotion workflow creates promotion workflow YAML files (for example, infrastructure/container/serverless promotions) based on metadata such as your team’s promotion-path.

This is typically used when you want a standardized promotion workflow per product/repo without manually authoring and maintaining the promotion YAML.

Workflow Reference

Repository: dojo360/pipelines-workflows
Workflow: .github/workflows/generate-promotion.yml
Docs: https://github.com/dojo360/pipelines-workflows/tree/main/web/generate-promotion/index.md

Key Features

• Validates deployment paths against metadata
• Generates workflow files under .github/workflows/ (promotion orchestration)
• Designed to integrate CI workflows + CD/promotion workflows

Prerequisites

• Dojo360 Metadata API onboarding (or equivalent metadata file) for your aide-id / team-name / domain
• Repository permissions that allow writing workflow files (GitHub workflow files are protected in some orgs)
• A clear target promotion type (infrastructure/container/serverless)

Required Inputs (Typical)

Exact inputs can vary by Dojo360 version; confirm against the Dojo360 docs.

Input	Type	Description
aide-id	string	AIDE ID used to fetch team metadata
team-name	string	Team name used for metadata lookup
domain	string	Domain used for metadata lookup
cloud-type	string	Cloud provider (e.g., awsOptum, azureOptum, gcp)
deployment-path	string	Hyphen-separated stages (e.g., dev-qa-cert-prod)

Common Optional Inputs (Typical)

Input	Type	Description
output-workflow-path	string	Where to write the generated workflow file (default is often .github/workflows/...)
promotion-workflow-type	string	Which promotion flavor to generate (infrastructure/container/serverless)
ci-workflow-file	string	CI workflow file name to integrate (optional)
cd-workflow-file	string	CD workflow file name to integrate (optional)

Templates

Ready-to-copy examples are in .github/skills/github-workflows-dojo360-generate-promotion/templates/:

• generate-infrastructure-promotion.yml
• generate-container-promotion.yml
• generate-serverless-promotion.yml

Notes / Gotchas

• Generated workflow files are code: treat them like any other change (review, PR, approvals).
• If your org restricts workflow file changes, you may need admin approvals or a specific branch policy.
• Prefer pinning Dojo360 workflows to @v2.0.0 rather than @beta for production stability.