use apt keyring instead of trusted.d #317
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.
In this PR, I'm trying to follow the recommendations from https://wiki.debian.org/DebianRepository/UseThirdParty to move away from trusted.d and use signed-by option with keyrings.
This should solve some error encountered when using puppetlabs-puppet module since the merge of puppetlabs/puppetlabs-puppet_agent#681 (eg. puppetlabs/puppetlabs-puppet_agent#681 (comment))
I was still not sure if in the case of puppetlabs-release we should rather put the keyring in
/etc/apt/keyrings
or/usr/share/keyrings
, feel free to correct me if needed.