launch-trigger-and-monitor-launch-deployments

Trigger a Launch deployment for a specific environment, then poll its status until completion. If the deployment fails or is cancelled, fetch the deployment log and diagnose likely causes with next-step recommendations.

Use when you need to automate Launch deployments for a known project and environment, monitor progress, and surface failure diagnostics. This is appropriate for CI/CD or operator workflows that need a deterministic deploy status check and log-based troubleshooting.

Users need a reliable way to start a deployment in Launch, track it to completion, and quickly understand why it failed if it does. The skill should reduce manual polling and make deployment failures actionable.

Deployment is triggered against the intended project and environment. Status is polled at a fixed interval until a terminal state is reached. The process exits non-zero on failed or cancelled deployments. If the deployment fails, the deployment log is retrieved and summarized with likely causes and next steps. Production targets are validated and require explicit confirmation before deployment.

• project_uid
• environment_uid
• Optional deployment payload or build reference
• Confirmation for production deployment when applicable
• Any available context about the app, branch, or build source

• Deployment UID and initial trigger response
• Current status updates during polling
• Terminal status and exit code
• Deployment log summary when failures occur
• Recommended next steps and probable root cause

• Trigger a deployment for project abc123 in environment prod456 and watch it until it finishes.
• Deploy the latest build to staging and tell me if it fails.
• If the deployment fails, check the logs and explain what went wrong.
• Poll a Launch deployment every 10 seconds and exit non-zero on failure.

Validate the project and environment identifiers. Confirm the target is allowed; require explicit approval for production. Trigger the deployment with the Launch API. Poll deployment status every 10 seconds until it reaches a terminal state. If status is failed or cancelled, fetch the deployment log and analyze it. Return a concise summary with status, log findings, and recommended next steps.

Return a concise deployment summary first. Include deployment UID, environment UID, and final status. On failure, include a short log-based diagnosis and next steps. Do not expose deployment tokens, secrets, or environment variables. Use a non-zero exit code for failed or cancelled deployments.

Use the Launch API for deployment trigger and status checks. Use the deployment detail/log endpoint for failure analysis. Validate the target environment before deploying. Require explicit confirmation for production deployments. Never auto-deploy to production without review.

• • Product: Launch
• • Description: Contentstack Launch: hosting, deployment, edge delivery, serverless functions, environment management, and CI/CD for Contentstack-powered frontends.
• • Product safety rules: - Never expose deployment tokens or environment secrets.
• Validate deployment targets before triggering.
• Require confirmation for production deployments.
• Never auto-deploy to production without review.
• • Default tools: ["Launch API", "Projects", "Environments", "Deployments", "Serverless Functions", "Edge Delivery", "Custom Domains"]
• • Default connectors: ["Launch Proxy", "GitHub", "CI/CD Pipelines"]