Rework the PGP key configuration #2085
Merged
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.
This PR adds a number of commits which work toward a better PGP key infrastructure inside Rustup.
In particular it adds (deliberately undocumented at this time) a
settings.toml
entrypgp_keys
and the environment variableRUSTUP_PGP_KEY
.We add a
PgpKey
enum which indicates where a key came from, so that we can use it in future debugging and/or informational messages to the user.Perhaps @dignifiedquire might take a look over this?