Add CLI tool to signature crate to check Balrog results#11459
Draft
oskirby wants to merge 5 commits into
Draft
Conversation
oskirby
force-pushed
the
rust-signature-cli-tool
branch
from
July 24, 2026 21:41
fd2693f to
bcab517
Compare
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.
Description
Following up from #11458 - the issue would have been easier to diagnose if there was a convenient tool that could check a Balrog update URL and print out some diagnostic details of the validation process. So, let's add such a tool as an example of the
signaturecrate.Reference
Related to: #11458
JIRA Issue: VPN-7720
Checklist
addons/strings.yaml.