deployment-readiness

Deployment Readiness

Assess deployment readiness, analyze environment drift, and make data-driven canary rollout decisions using Harness MCP.

Instructions

Step 1: Establish Scope

Confirm the service, target environment, and deployment type.

Call MCP tool: harness_list
Parameters:
  resource_type: "service"
  org_id: "<organization>"
  project_id: "<project>"

Step 2: Identify the Readiness Task

Determine which assessment the user needs:

1. Deployment Readiness Check -- Comprehensive pre-deploy validation with go/no-go
2. Environment Drift Analysis -- Differences between source and target environments
3. Canary Rollout Decision -- Data-driven promote, pause, or rollback recommendation

Step 3: Run Deployment Readiness Check

Gather from the user:

• Service name and target environment
• Deployment type (rolling, blue-green, canary)
• Change summary (what is being deployed)

Execute readiness checks:

Pipeline Health:

Call MCP tool: harness_list
Parameters:
  resource_type: "execution"
  org_id: "<organization>"
  project_id: "<project>"
  pipeline_id: "<pipeline_identifier>"

• Last N pipeline executions: pass rate and failure patterns
• All required stages passed (build, test, security scan)

Dependency Verification:

• All referenced connectors, secrets, and infrastructure are accessible
• Required approvals are configured for the target environment

Artifact Readiness:

• Container image exists and has passed security scanning
• SBOM is generated and signed (if required)
• Image tag matches the expected version

Environment Health:

• Target environment is not frozen or in maintenance
• No active incidents on the target cluster
• Resource capacity is sufficient for the deployment

Security Gates:

• No critical or high CVEs above threshold
• OPA policies pass for the target environment
• Required compliance attestations are present

Present a structured report with PASS/FAIL/WARNING for each check and a final GO/NO-GO recommendation.