execverb: env policy resolved through value providers #152
Labels
No labels
burndown-2026-06
sunday-sprint
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/cli-guard#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
The exec dialect could not set environment variables on the wrapped process, so an exec launcher could only reach whatever the inherited env pointed at (e.g. ollama's localhost OLLAMA_HOST), never a tailnet host - and an opaque host can't be hardcoded in the committed guardfile.
Add an
env <NAME> { value <provider> "<addr>" }block (child ofexec, sibling ofargv-prefix), plusenv "NAME" "literal"for committed values. The value resolves at exec time through a value provider, so an opaqueOLLAMA_HOSTcomes from SSM rather than the guardfile.To share the consumer's one provider registry across both engines, the Provider type + built-ins (env/file/literal) + Merge/Resolve move to a new
pkg/valuesource;specverb.Providerbecomes an alias. The generator wires the registry intomountExec(the AWS/SSM resolver block now triggers off exec members too), andexecverb.Describesurfaces each env var's source (never the resolved value).Implements the env-policy follow-up named in docs/execverb.md. Drives the OLLAMA_HOST-to-tower override for
ward-kdl agents ollama.