Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support to override keyring in aptly mirror create command #27

Open
mdechiaro opened this issue Jun 11, 2024 · 1 comment
Open

Add support to override keyring in aptly mirror create command #27

mdechiaro opened this issue Jun 11, 2024 · 1 comment

Comments

@mdechiaro
Copy link

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 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

mdechiaro added a commit to mdechiaro/puppet-aptly that referenced this issue Jun 25, 2024
@jay7x
Copy link
Member

jay7x commented Nov 26, 2024

Hi @mdechiaro! I see you made the change in your branch, but you did no PR here. Feel free to raise a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants