Handle the priority field correctly when a value is explicitly set #9
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.
I encountered the error
json: cannot unmarshal number into Go struct field keyslot.keyslots.priority of type string
when trying to unlock a volume that had had one of its keyslots boosted in priority with
cryptsetup config --priority prefer --key-slot 1 /dev/sda3
.This commit resolves it by using a pointer field to expose presence information.