Add Rust-first Spec API - #334
Open
domenkozar wants to merge 1 commit into
Open
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
secretspec | b0a748e | Commit Preview URL Branch Preview URL |
Aug 13 2026, 07:38 PM |
domenkozar
force-pushed
the
agent/rust-first-spec
branch
from
August 13, 2026 19:37
e991bb3 to
b0a748e
Compare
domenkozar
marked this pull request as ready for review
August 13, 2026 22:14
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
SpecAPI with builders for profiles, secrets, typed generation, and password character sets.CompiledSpecmodel.Secrets::from_specwhile keepingConfigas an internal TOML wire format.Why
Rust callers should be able to describe secrets directly without constructing a TOML-shaped configuration type or serializing and reparsing TOML. Making every frontend lower through
Specgives Rust-first and file-backed projects identical validation, inheritance, generation, and provider behavior.Developer impact
New integrations can build a
Specand pass it directly toSecrets::from_spec. Existing TOML projects continue to use the same syntax, but parsing now crosses the publicSpecabstraction. The old crate-rootConfigexport is removed because it represented the storage format rather than the supported semantic API.Validation
devenv shell cargo check --workspace --all-targetsdevenv shell cargo test -p secretspec spec::(6 passed)devenv shell cargo test -p secretspec cli::completion::tests(12 passed)devenv shell cargo test -p secretspec --lib(1,223 passed, 4 ignored)devenv shell cargo test -p secretspec-derive --test compile_testsdevenv shell npm --prefix docs run build