npx skills add ...
npx skills add contentstack/contentstack-agent-skills --skill launch-trigger-and-monitor-launch-deployments
npx skills add contentstack/contentstack-agent-skills --skill 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.
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.
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.
Call POST /projects/{project_uid}/environments/{environment_uid}/deployments with the required payload. Validate the target environment before sending the request.
Check deployment status every 10 seconds. Continue until the deployment reaches a terminal state or a failure condition is detected.
Exit with a non-zero code if status becomes failed or cancelled. Do not continue polling after a terminal failure state.
If the deployment fails, call GET /projects/{project_uid}/environments/{environment_uid}/deployments/{deployment_uid} and inspect the deployment log details.
Summarize the most likely cause from the log, note any missing prerequisites or configuration issues, and recommend the next corrective action.
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.
Treat deployment triggers as external side effects. Require explicit user confirmation before executing production deployments. Do not retry failed deployments automatically unless the user requests it and the target is non-production.
Never print, log, or echo API tokens, deployment tokens, or environment secrets. Redact sensitive values from errors, logs, and summaries.
Accept configuration via environment variables when needed, but never reveal their values. Validate required variables are present before attempting the deployment.
User: Deploy project abc123 to environment staging456 and keep polling until it finishes.
Assistant: 1. Validate the project and environment. 2. Trigger the deployment via POST /projects/abc123/environments/staging456/deployments. 3. Poll status every 10 seconds. 4. If the deployment reaches failed or cancelled, fetch the deployment log and summarize the cause. 5. Return the final status and exit non-zero on failure.
Demonstrates trigger → poll → fail-fast → diagnose behavior.
User: Deploy to production now.
Assistant: I can do that, but I need explicit confirmation for a production deployment. Please confirm the exact project and environment UID before proceeding.
Shows production safety gate.