> ## Documentation Index > Fetch the complete documentation index at: https://docs.ankra.ai/llms.txt > Use this file to discover all available pages before exploring further. # Promote a proven build into another environment (browser session) > Promote the build the source environment has proven into the target environment (ankra-ryfuy.38.4). Exactly one thing moves: the image tag the source runs, written into each target installation's stored deploy inputs and deployed through the same deploy_application job the Deploy button and push-to-deploy enqueue - never a rebuild, never configuration. The target's push-to-deploy watermark is stamped with the promoted build and one application_promotion row records the move. Refused (409) with one of the preview's blocker sentences verbatim: "Source environment is not serving a proven build", "Source environment's build cannot be identified", "Source environment's targets disagree on what they serve", "Target environment follows pushes", "Ankra could not read whether the target environment follows pushes", "Target environment has a deploy in flight", "Target environment is missing required secrets". A target already running the build answers 200 with state already_current and no deploy. Held to the applications.deploy permission. ## OpenAPI ````yaml https://platform.ankra.app/openapi.json post /org/applications/{application_id}/promotions openapi: 3.1.0 info: title: FastAPI version: 0.1.0 servers: - url: https://platform.ankra.app security: [] tags: - name: Organisation IAM description: >- Custom organisation roles and scoped role assignments for member and service-account identities. - name: Clusters description: Create, inspect and manage clusters, and the stacks deployed on them. - name: Managed Clusters description: Provider-managed control planes, driven through one common surface. - name: Imported Clusters description: Clusters that already existed and were connected to Ankra. - name: Cluster Access description: Kubeconfigs, service-account tokens and per-cluster access grants. - name: Kubernetes description: Read and act on the Kubernetes objects inside a cluster. - name: AWS Clusters description: >- Provision and manage self-managed k3s / kubeadm clusters on AWS EC2 in your own VPC. - name: Ankra Cloud Clusters description: >- Provision and manage self-managed kubeadm / k3s clusters on Ankra Cloud servers: a private network, a NAT router and a bastion per cluster. - name: DigitalOcean Clusters description: Provision and manage DigitalOcean Kubernetes clusters. - name: Hetzner Clusters description: Provision and manage Hetzner Kubernetes clusters. - name: OVH Clusters description: Provision and manage OVH Kubernetes clusters. - name: Scaleway Clusters description: Provision and manage Scaleway Kapsule clusters. - name: UpCloud Clusters description: Provision and manage UpCloud Kubernetes clusters. - name: Applications description: Deploy, configure and observe applications across the fleet. - name: Pipelines description: Pipeline definitions and the approval of the authority they declare. - name: Backups description: >- Backup vaults, restore points, protection posture and captures for stacks and application deployments; a completed capture is not a verified restore. - name: Stack Profiles description: Reusable stack definitions, their versions and sharing. - name: Services description: >- Versioned service packages and explicit sharing. Runtime admission is separate from publication. - name: Charts description: Browse the chart catalogue behind stacks and addons. - name: Helm description: Helm registries, credentials and the charts they expose. - name: Executions description: Long-running platform executions and their jobs. - name: Operations description: Cancel in-flight cluster operations and their jobs. - name: Chat description: Conversational sessions, plans and confirmable actions. - name: AI Management description: >- Customer agent lifecycle, authenticated identity and organisation automation controls. - name: AI Agent Runs description: Autonomous agent runs and their outcomes. - name: AI Tickets description: The AI ticket board, its sync connections and settings. - name: AI Playbooks description: Reusable playbooks the AI lanes execute. - name: AI Conditions description: Conditions that gate AI autonomy. - name: AI Remediation description: >- The organisation's auto-remediation policy: what the AI lanes may fix by themselves, and who approves the rest. - name: AI Engineering Handoffs description: Work the AI lanes escalate to a human engineer. - name: AI Environment description: The environment and base stacks AI demos deploy into. - name: Security description: Findings, advisories, SBOMs, compliance and posture. - name: Cost description: Cluster and fleet cost, rate cards and cost settings. - name: Decisions description: >- The decision ledger behind the Security and Cost queues: proposals a surface computed, the approve and set-aside decisions people took on them, and the receipts of running them. - name: Billing description: Subscription and spend caps. - name: Organisation description: Members, invitations, audit logs and organisation settings. - name: Account Tokens description: Personal access tokens for the API and CLI. - name: Credentials description: The shared credential store. - name: AWS Credentials description: >- AWS credentials: access keys or CloudFormation-onboarded STS roles for cost, EKS and self-managed provisioning. - name: Ankra Cloud Credentials description: >- Ankra Cloud API tokens, shared by the self-managed and managed Ankra Cloud lanes. - name: Azure Credentials description: Azure credentials and SSH keys. - name: DigitalOcean Credentials description: DigitalOcean credentials and SSH keys. - name: Hetzner Credentials description: Hetzner credentials and SSH keys. - name: OVH Credentials description: OVH credentials and SSH keys. - name: Scaleway Credentials description: Scaleway credentials. - name: UpCloud Credentials description: UpCloud credentials and SSH keys. - name: Data Source Credentials description: Credentials for metrics and log sources. - name: DNS Credentials description: Credentials for DNS providers. - name: Object Storage Buckets description: >- Buckets Ankra creates and manages on an organisation's own provider credentials. - name: DNS description: DNS zones and records, including custom organisation zones. - name: Cloudflare description: Cloudflare domains and the credentials behind them. - name: Variables description: Organisation- and cluster-scoped variables. - name: SOPS description: Encrypt and decrypt values with the organisation SOPS config. - name: Alerts description: Alert integrations and ingest credentials. - name: Notifications description: Notification routes and their delivery targets. - name: Support description: Support tickets. - name: AI Settings description: Organisation AI provider, model catalog and per-function model settings paths: /org/applications/{application_id}/promotions: post: tags: - Applications summary: Promote a proven build into another environment (browser session) description: >- Promote the build the source environment has proven into the target environment (ankra-ryfuy.38.4). Exactly one thing moves: the image tag the source runs, written into each target installation's stored deploy inputs and deployed through the same deploy_application job the Deploy button and push-to-deploy enqueue - never a rebuild, never configuration. The target's push-to-deploy watermark is stamped with the promoted build and one application_promotion row records the move. Refused (409) with one of the preview's blocker sentences verbatim: "Source environment is not serving a proven build", "Source environment's build cannot be identified", "Source environment's targets disagree on what they serve", "Target environment follows pushes", "Ankra could not read whether the target environment follows pushes", "Target environment has a deploy in flight", "Target environment is missing required secrets". A target already running the build answers 200 with state already_current and no deploy. Held to the applications.deploy permission. operationId: start_application_promotion parameters: - in: path name: application_id required: true schema: type: string title: Application Id requestBody: content: application/json: schema: $ref: '#/components/schemas/StartApplicationPromotionRequest' required: true responses: '200': content: application/json: schema: $ref: '#/components/schemas/ApplicationPromotionResponse' description: Successful Response '403': content: application/json: schema: $ref: '#/components/schemas/DemoDetailError' description: You do not have permission to promote deploys of this application. '404': content: application/json: schema: $ref: '#/components/schemas/DemoDetailError' description: Not found ("Application not found" or "Environment not found") '409': content: application/json: schema: $ref: '#/components/schemas/DemoDetailError' description: A blocker the preview would have listed, as its sentence verbatim '422': content: application/json: schema: $ref: '#/components/schemas/DemoDetailError' description: >- "Source and target environments must differ.", or a body missing source_environment_id / target_environment_id components: schemas: StartApplicationPromotionRequest: description: The two environments, by the ids the environments read answers with. properties: source_environment_id: type: string target_environment_id: type: string expected_fingerprint: type: string description: >- Optional concurrency precondition. A changed reviewed source or target returns 409. Required by the new managed portal; omitted only by legacy immediate-promotion callers. required: - source_environment_id - target_environment_id title: StartApplicationPromotionRequest type: object ApplicationPromotionResponse: properties: promotion_id: anyOf: - type: string - type: 'null' description: 'null when nothing was written: the target already ran the build.' state: type: string enum: - promoted - already_current image_tag: type: string commit_sha: type: string previous_image_tag: anyOf: - type: string - type: 'null' description: >- What the target ran when the promotion was requested; null when that could not be read, never when nothing ran. operation_id: anyOf: - type: string - type: 'null' description: >- The deploy execution carrying the outcome; null when no deploy was enqueued. source: $ref: '#/components/schemas/ApplicationPromotionEnvironment' target: $ref: '#/components/schemas/ApplicationPromotionEnvironment' operation_ids: anyOf: - items: type: string format: uuid type: array - type: 'null' description: >- Every target deployment operation; empty or null when already current. required: - promotion_id - state - image_tag - commit_sha - previous_image_tag - operation_id - source - target title: ApplicationPromotionResponse type: object description: >- The write's answer. A target environment with several installations (one per namespace) is promoted as one row and one deploy execution per installation; promotion_id and operation_id are the first installation's. DemoDetailError: description: >- The FastAPI-style detail envelope the demo routes use for 400/403/404/409/502 responses. properties: detail: type: string required: - detail type: object ApplicationPromotionEnvironment: description: >- One side of a promotion. id is the environment's id (a cluster id in wave-1 identity). properties: id: type: string name: type: string role: type: string required: - id - name - role title: ApplicationPromotionEnvironment type: object ````