base-layer/commandkit
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 5 Wiki Activity

Demonstrate composed configuration comparison

Browse Source
This commit is contained in:
Eric Rakestraw
2026-10-11 21:54:39 +00:00
parent 3cbb1f35b0
commit f0853d1000
6 changed files with 243 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
integrations/ckprompt/examples/composed/README.md
View File

@@ -6,6 +6,8 @@ definition inspection, and one application-owned command:
```sh
go run . config scopes
go run . config validate --scope all --campaign spring --limit=0
go run . config diff --scope app --config fixtures/before.yml --against-config fixtures/after.yml
go run . config diff --scope app --config fixtures/before.yml --against-config fixtures/after.yml --campaign spring --limit=0
go run . promptkit show prompt briefing --campaign spring --format yaml
go run . promptkit show profile spring --campaign spring
go run . session restore session-42 --campaign spring
@@ -20,3 +22,12 @@ cache independently for its invocation, using the same application and engine
loader functions. See the
[consumer guide](https://gitea.maximumdirect.net/eric/CommandKit/src/branch/main/docs/consumers/guide.md)
and the suites' GoDoc for initialization timing and ownership.
The application-scope comparison loads the local `before.yml` and `after.yml`
fixtures and reports `changes.default_campaign: autumn`. The second invocation
supplies `spring` to both sides, so the effective defaults compare equal; the
application input check also requires `--limit=0` when `--campaign` is supplied.
The example's shared run cache keys successful results by the complete supplied
configuration/overlay selection and the supplied campaign, including presence.
The campaign override is applied through ConfigKit before loading. These are
choices for this example's loader and do not define a CommandKit cache policy.