Repository navigation
feat(proto): bump flintlock API to v0.11.0 + expose version - #21
Merged
Merged
Conversation
Update the vendored/pinned flintlock protos from v0.9.1 to v0.11.0 (latest).
The upstream diff is purely additive and wire-compatible:
- MicroVMSpec.allow_guest_agent (bool, field 17)
- MicroVMStatus.vsock_path (string, field 7)
The MicroVM service definition is unchanged, so the drop-in flintlockd
contract is preserved. Regenerated stubs pick up the new fields; Brigade
forwards specs verbatim so no server handling is needed.
Also expose the implemented flintlock API version so operators can confirm
which contract Brigade serves:
- New config :brigade, flintlock_api_version ("v0.11.0") as the single
source of truth.
- Surfaced on GET /status via Status.snapshot/0.
- mix proto.bump now rewrites the config pin (update_config_pin/1),
keeping it in lockstep with the README pin on future bumps.
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
1 participant
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
Update the vendored/pinned flintlock protos from v0.9.1 → v0.11.0 (latest upstream, released 2026-07-22) and expose the implemented API version on
GET /status.API diff (v0.9.1 → v0.11.0)
Purely additive / wire-compatible — no breaking changes:
MicroVMSpec.allow_guest_agent—bool, field 17 (vsock device for in-guest guest-agent)MicroVMStatus.vsock_path—string, field 7 (host UDS path for the vsock device)The
MicroVMservice definition is unchanged, so the drop-inflintlockdcontract is preserved. Regenerated stubs pick up the new fields; Brigade forwards specs verbatim, so noserver.exhandling is needed. Guest-agent enablement is out of scope here.Expose the version
Operators / clients can now confirm which flintlock contract Brigade serves:
config :brigade, flintlock_api_version: "v0.11.0"— single source of truth.GET /statusviaStatus.snapshot/0.mix proto.bumpnow rewrites the config pin (update_config_pin/1), keeping it in lockstep with the README pin on future bumps.Verification
mix formatclean,mix compile --warnings-as-errorsclean.mix test→ 34 tests + 1 doctest, 0 failures.git diff proto/vendor/shows only the two additive fields.observability_test.exsasserts the version in bothStatus.snapshot/0and the/statusJSON body.