{{ message }}
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.

There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One subtle change from the existing logic: instead of retrieving both the default target (
trusted_root.json) AND the tenant-prefixed target (some-trust-domain.trusted_root.json), the new logic will retrieve ONLY the tenant-prefixed version if the--hostnameflag is supplied.If you're identifying a specific tenant with the
--hostnameflag it seems reasonable to assume that you're only interested in the trusted root associated with that tenant.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Seems fair. PGI is always included though. Given that a properly configured policy is configured, there would be no risk of confusion here during verification.