minco-plan 1.12.0

Deployment plans, database cost profiles, structural policy checks, and AWS SAM rendering for Minco
Documentation

minco-plan

Provider-neutral deployment planning for Minco.

The Plan IR connects OpenAPI operations to runtime, ingress, authentication, the configured static application graph, database, performance, and cost-policy decisions. Schema 2 explicitly models one HTTP API function, worker functions, queues, dead-letter policy, SQS mappings and reviewed schedule triggers. Schema 1 remains supported for the original API-only topology.

Schema 2 checks stable references and CloudFormation identities, function and mapping concurrency, aggregate connection pressure, queue visibility and retention, FIFO/redrive compatibility, partial-batch responses and minimal-idle schedule policy. It derives typed IAM intent rather than accepting secret values or free-form policy documents.

Cost output classifies structural dimensions as zero_compute, request_only, storage_only, scheduled_wakeup or fixed_monthly, with priced, unpriced, region_dependent, free_tier_dependent or eligibility_dependent pricing confidence. Provider allowances never become a complete zero-dollar estimate solely because current usage fits.

It also records only the AWS service set needed for local adapter conformance and can render deterministic AWS SAM/CloudFormation for PostgreSQL-compatible API/worker topologies. Local topology never runs schedules. Generic DynamoDB SAM fails closed because its table and IAM must be declared by an access-pattern-specific adapter.

An explicitly selected static-site intent can add a retained, encrypted, publicly blocked S3 bucket, CloudFront OAC with SigV4 signing, an explicit cache policy, SPA fallback, and optional certificate/Route 53 parameters. The default plan remains API-only and adds none of those resources. An optional one-time schedule cleanup contract records ActionAfterCompletion: DELETE, residual resources and a manual fallback; it is rejected for recurring schedules. SAM rendering fails closed because the current SAM and CloudFormation schedule schemas do not expose that Scheduler API property. allowed_origins and allowed_headers are exact configuration inputs: empty, wildcard, invalid, and duplicate header lists are rejected, and the normalized values are carried into both Plan IR and generated SAM CORS policy. The derived exposed_headers inventory makes Minco's frontend-neutral response metadata visible in Plan IR and is rendered directly into the SAM CORS policy. A plugin that requires an additional browser request header must have that header explicitly represented in the selected application configuration.

Applications can also opt into a typed HttpTrafficPolicy when rendering the AWS topology. It maps one optional default request-rate/burst target plus operation-ID overrides to API Gateway HTTP API DefaultRouteSettings and RouteSettings on both Minco's default and candidate stages. The ordinary render_sam* functions remain unchanged when no policy is selected, preserving the frozen 1.x deployment-plan schema and existing output. This is coarse best-effort ingress protection, not a per-user distributed limiter or hard cost ceiling; it adds no Redis service, worker, schedule, provisioned compute, or application request-path counter. See docs/how-to/api-traffic-policy.md.

Applications should treat the generated plan as reviewable deployment evidence, not as an exact cloud bill forecast.

An explicit preview plan adds a bounded owner and TTL, expected account/Region, sorted CloudFormation resource identities, delete/retain policy, and structural idle-cost classes. Pricing may remain visibly incomplete. Expiry adds no scheduled wakeup by default. An opt-in one-time cleanup remains a visible scheduled_wakeup, requires delete-after-completion metadata and a manual fallback, and is not rendered into an implicit hosted controller.

See docs/deployment/plan-schema-v2-migration.md for the schema 2 compatibility boundary and explicit upgrade procedure.