Take the configuration surface back from keel #54
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "land/keel-ten"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
deps: take the configuration surface back from keel
keel 0.10 is a library that reads no file and no environment variable, so
keel::configis gone:load,Config,Hold,NAME, and the adaptorstore fragments with it. ensign declares what it needs and opens its own
store. keel moves 0.9.0 to 0.10.2, plumb 0.5.0 to 0.18.5, and Sealkit back
to no version requirement — the doctor now reads all three as current.
Runtimegrowslistenandcache, and owns the filename:ensign.tomlrather than borrowing keel's.
[identity]is not a section any more — theunit is named in code where
identifyis called — so it leaves the fileentirely.
What this actually cost was not the six call sites in the product. It was
the copies of that file living in scaffolding, none of which fail to
compile and all of which fail silently:
keel.tomlcarrying[identity], so thebinary found no store configuration and four of five tests broke;
on the default while the harness polled the other one;
image.
The guard gains
cargo check --release, which Plumb 0.18.5 now requiresof a Rust repository — and which keel 0.10.0 and 0.10.1 would have failed.