IDP: Validate provisioning map against schema #122
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
|
@tdewey-rpi This schema enables validation of the Provisioning Map component of the Image Description JSON (ie the part which defines how the image should be provisioned on-device). |
Introduce schema validation of the Provisioning Map (PMAP). The schema is selected by a new base image layer config variable, with default schemas residing under layer/base/schemas/provisionmap/. The generic post-image hook now validates the PMAP automatically on every build. This ensures the staged JSON is valid for the provisioning side to process. Drop (now redundant) checks on some JSON objects in the pmap helper. Schema validation is performed on every invocation. Clarify some description wording in the AB layer. Fixup bad partition ref in the AB layer clear pmap for A.system. Update docs.
tdewey-rpi
reviewed
Oct 31, 2025
docs/layer/image-rota.html
Outdated
| System B will be provisioned encrypted (hybrid). Development only.</td> | ||
| clear: All partitions will be provisioned unencrypted. | ||
| crypt: All partitions except <slot>:boot will be provisioned encrypted. | ||
| hybrid: B:system will be provisioned encrypted (development only).</td> |
There was a problem hiding this comment.
We should also consider the reverse-hybrid (read: just-what-matters), where you only encrypt the userdata partition.
There was a problem hiding this comment.
Ack. hybrid is just for testing, but I agree we probably need more granularity regarding what gets encrypted. I'll add some follow-up commits to tweaks the types of pmap that we support here.
|
Hi @tdewey-rpi |
Add two new PMAPs: - cryptdata : Only the persistent storage partition is encrypted. - cryptslots : Only the system (OS) partition for each slot is encrypted. Rename hybrid -> crypthybrid - this is a development-only PMAP which encrypts B.system. A crypt* PMAP now denotes encryption will be applied on some part of the disk image at provisioning time. Schema header, PMAP versions and documentation updated.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Introduce schema validation of the Provisioning Map (PMAP). The schema is selected by a new base image layer config variable, with default schemas residing under layer/base/schemas/provisionmap/.
The generic post-image hook now validates the PMAP automatically on every build. This ensures the staged JSON is valid for the provisioning side to process.
Drop (now redundant) checks on some JSON objects in the pmap helper. Schema validation is performed on every invocation.
Clarify some description wording in the AB layer.
Fixup bad partition ref in the AB layer clear pmap for A.system.