Add BootReleaseSet and EnrollmentToken examples#60
Merged
Conversation
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.
Summary
Adds concrete boot provisioning examples for the existing
BootReleaseSetandEnrollmentTokencontrol-plane schemas.This PR adds:
examples/boot_release_set.jsonexamples/enrollment_token.jsonThis PR updates:
tools/validate_control_plane_examples.pyexamples/README.mdWhat changed
The examples model the M2 secure recovery/provisioning lane:
BootReleaseSetlinks recovery boot artifacts to the assignedReleaseSetEnrollmentTokenauthorizes one-time recovery access for the M2 demo deviceReleaseSet,Fingerprint,BootReleaseSet, andEnrollmentTokenThe example uses non-operational artifact URNs rather than live URLs so it remains a safe contract example, not a runnable remote boot instruction.
Software review
Correctness: this extends the existing control-plane lifecycle proof from assignment + fingerprint into secure boot/recovery authorization without duplicating schemas.
Risk: low. Spec/example/validation-only tranche.
Weakness: this does not yet define a richer signed boot manifest schema or nlboot wire protocol; it uses the existing minimal BootReleaseSet/EnrollmentToken contract.