Skip to content

chant on GCP and Azure

llms.txt lists every page for an agent

For a team on Google Cloud or Azure: Config Connector resources and ARM templates from TypeScript, with a local emulator for each cloud.

Works

  • GCP Config Connector resources and Azure ARM templates from TypeScript
  • Local deploys to floci-gcp through gcpApply and to floci-az through azApply, with no account
  • GKE and AKS clusters with their workloads from the Kubernetes lexicon, in one project

Differs

By forge

  • --generate github writes the pull-request workflow under .github/workflows/, run on pull_request and on push to the target branch.
  • Both jobs use the job's own github.token. On a pull request from a fork that token is read-only, so the plan note and the status are not posted.

First step

For Azure, use azure in place of gcp.

Terminal window
npm install --save-dev @intentius/chant-lexicon-gcp
npx chant init my-infra --lexicon gcp

Local Testing

Or hand this step to your coding agentIt stops at a pull request or a report.
Show the whole prompt
Read https://intentius.io/chant/for/gcp-azure/.
Set up chant in this repository with the gcp lexicon, or the azure lexicon when the repository targets Azure; use `azure` in place of `gcp` below.
Install it with `npm install --save-dev @intentius/chant-lexicon-gcp`, run `npx chant init . --lexicon gcp`, and read every `skills/*/SKILL.md` it writes before you author anything.
Run `npx chant build` and `npx chant lint` until both pass, and open a pull request with the result. Deploy only to the local emulator (floci-gcp or floci-az), and only when I ask.
Never deploy to a real cloud account or shared environment (with `chant run`, `chant components` or a platform's own CLI), approve (a pull request review, `chant approve` or `chant run approve`), override a policy denial (`chant approve policy-override`), or merge; never cut or publish a release (`chant release cut --yes` or `chant release publish`), push or delete a `ci/*` tag (`chant ci tick` pushes them), or change the value of an existing flag; never touch `.chant/allowed_signers` or `chant/lifecycle`.

Proof

Example projects in the chant repository for this room, each with a README that has the commands to run it. The last rows count the examples each lexicon ships, read from the repository when this site was built.

ExampleWhere
local-cloud-trio examples/local-cloud-trio
k8s-gke-microservice examples/k8s-gke-microservice
k8s-aks-microservice examples/k8s-aks-microservice
cockroachdb-multi-region-gke examples/cockroachdb-multi-region-gke
8 examples lexicons/gcp/examples
13 examples lexicons/azure/examples

Then read

Tasks
Local testing on GCPLocal testing on AzureGCP GKE + KubernetesAzure AKS + KubernetesCockroachDB Multi-RegionRay + KubeRay on GKE
Background
Choosing Your Deployment ModelWhere Values Come From
Reference
GCP Config Connector lexiconAzure ARM lexicon

chant