You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Affected Puppet, Ruby, OS and module versions/distributions
Puppet: N/A
Ruby: N/A
Distribution: N/A
Module version: 2.1.0
How to reproduce (e.g Puppet code you use)
N/A
What are you seeing
The keyring parameter is available as a class parameter, but it isn't exposed in the aptly mirror createcommand, so it cannot be used to set custom location of keys. When this flag is absent, then the default location according to the docs is in ~/.gnupg/trustedkeys.gpg.
What behaviour did you expect instead
The ability to override keyring in aptly mirror create command.
Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered:
mdechiaro
added a commit
to mdechiaro/puppet-aptly
that referenced
this issue
Jun 25, 2024
Affected Puppet, Ruby, OS and module versions/distributions
How to reproduce (e.g Puppet code you use)
N/A
What are you seeing
The
keyring
parameter is available as a class parameter, but it isn't exposed in theaptly mirror create
command, so it cannot be used to set custom location of keys. When this flag is absent, then the default location according to the docs is in~/.gnupg/trustedkeys.gpg
.What behaviour did you expect instead
The ability to override keyring in
aptly mirror create
command.Output log
Any additional information you'd like to impart
The text was updated successfully, but these errors were encountered: