container: Allow alternative formatting to drop ostree-unverified-registry
#604
Conversation
This file contains 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
…gistry` Since ostreedev@34fea14 we are backing off the signature verification bits. Let's make it easier to not put those bits in the user's face by adding an alternative formatting that drops it if it's the default.
cgwalters
added a commit
to cgwalters/bootc
that referenced
this pull request
Feb 13, 2024
Same motivation as ostreedev/ostree-rs-ext#604 Because fetching from a registry with the default sigverify is the 90% case default, when we see this (and are formatting for human consumption), use the "alternate" formatting to just display the image name. This makes the ostree stuff *much* less in the user's face in the default path.
cgwalters
added a commit
to cgwalters/bootc
that referenced
this pull request
Feb 13, 2024
Same motivation as ostreedev/ostree-rs-ext#604 Because fetching from a registry with the default sigverify is the 90% case default, when we see this (and are formatting for human consumption), use the "alternate" formatting to just display the image name. This makes the ostree stuff *much* less in the user's face in the default path. Signed-off-by: Colin Walters <walters@verbum.org>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this pull request
Feb 13, 2024
Same motivation as ostreedev/ostree-rs-ext#604 Because fetching from a registry with the default sigverify is the 90% case default, when we see this (and are formatting for human consumption), use the "alternate" formatting to just display the image name. This makes the ostree stuff *much* less in the user's face in the default path. Signed-off-by: Colin Walters <walters@verbum.org>
cgwalters
added a commit
to cgwalters/bootc
that referenced
this pull request
Mar 18, 2024
Followup to e3db010 where this one was missed. Copy-pasting that git log for ease of consumption: Same motivation as ostreedev/ostree-rs-ext#604 Because fetching from a registry with the default sigverify is the 90% case default, when we see this (and are formatting for human consumption), use the "alternate" formatting to just display the image name. This makes the ostree stuff *much* less in the user's face in the default path. Signed-off-by: Colin Walters <walters@verbum.org>
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.
Since
34fea14 we are backing off the signature verification bits. Let's make it easier to not put those bits in the user's face by adding an alternative formatting that drops it if it's the default.