/**
 * Phase 4 Pipeline -- Stage 7: Deployment Generator
 *
 * Generates cloud-provider-specific deployment descriptors based on the
 * cloudProvider field in ERPResolution:
 *
 *   gcp (default)  -- Cloud Run: Knative YAML, Cloud Build, GCP .env.example
 *   aws            -- ECS/Fargate: task-definition.json, buildspec.yml, AWS .env.example
 *   azure          -- Container Apps: container-app.yaml, azure-pipelines.yml, Azure .env.example
 *   alibaba/on-prem -- Dockerfile + generic .env.example (no orchestrator-specific files)
 *
 * The Dockerfile is cloud-agnostic and shared across all providers.
 *
 * TypeScript target: Node 20 multi-stage Docker build.
 * Rust target: Rust 1.77 / Debian bookworm-slim multi-stage Docker build.
 *
 * All generated files carry a "do not edit manually" header.
 *
 * Exports:
 *   - generateDeployment(context) -- pipeline entry point
 *
 * Error codes:
 *   ECLI-P4-070  Missing prerequisite stage output (erp-target-resolution)
 *   ECLI-P4-071  Deployment file write failure
 */
import type { Phase4Context, Phase4StageOutput } from '../types.js';
/**
 * Stage 7 entry point: generate cloud-provider-specific deployment descriptors.
 *
 * Reads ERPResolution from context.stageOutputs.get('erp-target-resolution'),
 * checks cloudProvider to determine which deployment templates to generate,
 * derives a short trace ID suffix, and writes all deployment files to
 * phase4/deployment/.
 *
 * Supported providers:
 *   - gcp (default): Cloud Run + Cloud Build
 *   - aws: ECS/Fargate + CodeBuild
 *   - azure: Container Apps + Azure DevOps Pipelines
 *   - alibaba, on-prem: Dockerfile + generic .env.example
 *
 * @param context - The Phase 4 pipeline context
 * @returns Stage output describing success or failure
 */
export declare function generateDeployment(context: Phase4Context): Phase4StageOutput;
//# sourceMappingURL=deployment-generator.d.ts.map