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
gcpApplyand to floci-az throughazApply, with no account - GKE and AKS clusters with their workloads from the Kubernetes lexicon, in one project
Differs
By forge
--generate githubwrites the pull-request workflow under.github/workflows/, run onpull_requestand onpushto 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.
--generate gitlabwrites.gitlab-ci.yml, andapplyruns one at a time per environment throughresource_group.- A CI job token cannot write merge request notes, so set a project access token with the
apiscope as the masked variableCHANT_FORGE_TOKEN.
--generate forgejowrites the GitHub workflow in the Forgejo dialect under.forgejo/workflows/: the runner label, action references by URL, and nopermissionsblock.- Forgejo workflows are GitHub-dialect, so
chant auditapplies its GitHub rules to them.
First step
For Azure, use azure in place of gcp.
npm install --save-dev @intentius/chant-lexicon-gcpnpx chant init my-infra --lexicon gcpShow 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.
| Example | Where |
|---|---|
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 |