From 3a4fb85188a1cb4d715c4da4c96fb04013e28a7d Mon Sep 17 00:00:00 2001 From: lex00 <121451605+lex00@users.noreply.github.com> Date: Sat, 17 Oct 2026 12:47:48 -0600 Subject: [PATCH] choudoufu: AWS and Kubernetes with more on the way, not experimental Co-Authored-By: Claude Opus 5.5 (1M context) --- src/content/docs/compare/choudoufu-and-terraform-state.md | 2 +- src/content/docs/compare/control-planes.md | 2 +- src/content/docs/tools.mdx | 2 +- src/content/docs/work.md | 2 +- src/data/rooms.mjs | 2 +- 5 files changed, 5 insertions(+), 5 deletions(-) diff --git a/src/content/docs/compare/choudoufu-and-terraform-state.md b/src/content/docs/compare/choudoufu-and-terraform-state.md index 8dc0131..daa15af 100644 --- a/src/content/docs/compare/choudoufu-and-terraform-state.md +++ b/src/content/docs/compare/choudoufu-and-terraform-state.md @@ -22,7 +22,7 @@ Twenty of them, each a scenario that runs in a few minutes. Every one also runs ## Where it stops -AWS only, and experimental. About half the provider's types carry no tags, so they are identifiable but not governable by a tag condition. The identity of a resource has to be knowable before it is created, and a read-only check reports what refuses before you commit to anything. +choudoufu runs on AWS and Kubernetes, with more platforms on the way. A missing resource type is rarely what stops a configuration. A `backend "s3"` block, a non-default workspace or a `count.index` in a resource name usually stops it first. `choudoufu live-check` reads your configuration and reports anything it would refuse before you commit to anything.