The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Jun 10, 2026 6:32pm

PR Summary

Medium Risk
Mutating operations (start/stop/retry/approve) can change live deployments; routes accept AWS keys in the body like other AWS tools but are gated by internal auth and follow the existing tool pattern.

Overview
Adds a full AWS CodePipeline integration so workflows can list pipelines, inspect state and executions, start/stop runs, retry failed stages, and submit manual approval decisions.

Eight authenticated /api/tools/codepipeline/* routes call the AWS SDK v3 client with Zod boundary contracts, shared awsErrorStatus mapping, and matching tool definitions plus a CodePipeline workflow block (operation dropdown, AWS key fields, templates/skills). Docs, integrations.json, icon mappings, block/tool registries, @aws-sdk/client-codepipeline, and the API validation route baseline (804 → 811) are updated accordingly.

^{Reviewed by Cursor Bugbot for commit 1a5a510. Bugbot is set up for automated code reviews on this repo. Configure here.}

Greptile Summary

Adds an AWS CodePipeline integration with 8 tools (start/stop execution, get pipeline state, get/list executions, list pipelines, retry stage, put approval result) backed by server-side AWS SDK v3 routes, a CodePipeline block with operation dropdown, Zod-validated contracts, and a generated docs page.

• API routes (apps/sim/app/api/tools/codepipeline/): Each of the 8 operations has its own Next.js route with internal-auth gating, Zod contract validation, and a shared awsErrorStatus helper that propagates 4xx codes from the AWS SDK $metadata field rather than always returning 500.
• Block (apps/sim/blocks/blocks/codepipeline.ts): Conditional subblocks per operation, robust pipelineVariables table parsing via parseOptionalJsonInput (which wraps JSON.parse in a try/catch), correct user-only visibility on all AWS credential params, and 8 BlockMeta templates plus 4 skills.
• Contracts (apps/sim/lib/api/contracts/tools/aws/): Input schemas enforce AWS-aligned limits (pipeline name ≤ 100 chars, retryMode as enum, summary min/max, clientRequestToken character set regex) with validateAwsRegion on all routes.

Confidence Score: 5/5

Safe to merge — all eight routes are correctly guarded by internal auth and Zod contract validation, the shared awsErrorStatus helper properly propagates AWS 4xx codes, and the pipelineVariables JSON parsing is safely wrapped.

The integration follows established patterns from other AWS integrations in the codebase. Both issues flagged in the previous review thread (AWS error status mapping and unguarded JSON.parse) are addressed. AWS credentials use user-only visibility consistently across all tool params. Input validation is thorough with AWS-aligned length constraints and enum validation for retryMode and approval status. No logic bugs or data-loss paths were found.

No files require special attention.

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Block as CodePipeline Block
    participant Tool as Tool Config (params fn)
    participant Route as /api/tools/codepipeline/<op>
    participant Auth as checkInternalAuth
    participant Zod as Zod Contract Validation
    participant AWS as AWS CodePipeline SDK

    Block->>Tool: operation + block params
    Tool->>Tool: parseOptionalJsonInput / parseOptionalNumberInput / parseOptionalBooleanInput
    Tool->>Route: "POST { region, accessKeyId, secretAccessKey, ...opParams }"
    Route->>Auth: checkInternalAuth(request)
    Auth-->>Route: "{ success, userId }"
    Route->>Zod: parseToolRequest(contract, request)
    Zod-->>Route: validated body or 400 error
    Route->>AWS: "new CodePipelineClient({ region, credentials })"
    AWS-->>Route: response or error
    Note over Route,AWS: awsErrorStatus maps 4xx from $metadata
    Route-->>Block: "{ success: true, output } or { error, status: 4xx/5xx }"

_{Reviews (3): Last reviewed commit: "fix(codepipeline): address review feedba..." | Re-trigger Greptile}

@greptile review

@greptile review