Control Plane

The cpln lexicon declares Control Plane infrastructure as typed chant resources. Control Plane is a hybrid multi-cloud platform: workloads deploy into Global Virtual Clouds that span AWS, GCP, Azure and private clouds, with geo-routing, TLS termination and identity-based cloud access handled by the platform.

Types are generated from Control Plane’s served OpenAPI document (https://api.cpln.io/openapi.json), so they track the real API.

Install it with:

npm install --save-dev @intentius/chant-lexicon-cpln

Quick Start

import { Gvc, Workload } from "@intentius/chant-lexicon-cpln";

export const gvc = new Gvc({
  name: "prod",
  spec: {
    staticPlacement: {
      locationLinks: ["/org/acme/location/aws-us-east-1"],   // placement is GVC-level
    },
  },
});

export const web = new Workload({
  name: "web",
  gvc: "prod",
  spec: {
    type: "serverless",                                       // exactly one HTTP port
    containers: [{
      name: "main",
      image: "nginx:1.27",
      ports: [{ number: 8080, protocol: "http" }],
    }],
    firewallConfig: {
      external: { inboundAllowCIDR: ["0.0.0.0/0"] },          // closed by default
    },
  },
});

The loop

1. chant build — synthesize and lint. The CPL rules catch the silent failures Control Plane does not report: an unqualified identity link, a scale-to-zero that never happens, a secret reference with no field.
2. cpln apply --file dist/cpln.yaml --ready — reconcile. Ordering across documents is resolved by cpln apply itself.
3. chant plan — read the live org back and diff. Ownership comes from the tags marker chant stamps at synthesis.

At a Glance

Metric	Count
Resources	8
Property types	142
Services	1
Intrinsic functions	0
Pseudo-parameters	0
Lint rules	22

Lexicon version: 0.53.1
Namespace: Cpln

• All Rules — 22 rules
• Serialization — output format details