See the

puppetlabs-firewall

module at https://forge.puppet.com/puppetlabs/firewall?src=slack&channel=voxpupuli

My apologies if this isn't the correct place. I wanted to suggest an enhancement to puppetlabs-sshkeys_core that it purge (on linux) /etc/ssh/ssh_known_hosts of unmanaged entries but the Issues tab is not available/enabled. Before I make too much of a fool of myself, does anyone know if the purge option was discussed? I looked over closed Pull Requests but I didn't find anything. Since this is a core resource I'm sure this is a fairly significant request.

@Brian Schonecker that's a module owned by puppetlabs, I suggest to ask in #puppet and maybe highlight craig gumbley and ask how to adress this

because I thi k issues are disabled by accident

it's not by accident

(were not enabled again which should have happened)

it's related to some struggles they have with jira migration

someone mentioned it before

as far as I know the CAT reenabled github issues for puppetlabs modules?

and then disabled it when they fail to migrate

so it's a mess

how does github and jira relate?

tickets

I know they disabled some jira boards again due to the migration

but github issues?

@Brian Schonecker you might want to look into puppet/augeasproviders_ssh

See the

puppet-augeasproviders_ssh

module at https://forge.puppet.com/puppet/augeasproviders_ssh?src=slack&channel=voxpupuli

You should be able to purge sshkeys either with

resource

resource (yep twice) or purge resource from crayfishx/purge

See the

crayfishx-purge

module at https://forge.puppet.com/crayfishx/purge?src=slack&channel=voxpupuli

Or per user with https://www.puppet.com/docs/puppet/6/types/user.html#user-attribute-purge_ssh_keys

he asked about host keys, I think

does anyone have a way to reach out to saz?

This message was deleted.

sometimes you have to be a pest to get things moving :P speaking of @bastelfreak, you up for a review of https://github.com/voxpupuli/puppet-openssl/pull/164? Xd

So, I've got a slightly weird situation that I'm not sure is 100% covered in the "Migrating a module to Vox Pupuli" documentation: I've got a module that I'm interested in donating to Vox Pupuli (if you're interested in having it), but, I can no longer maintain it myself as we're no longer using the software managed with it (indeed that's the reason I want to transfer it). I do know that there are other users who are interested in the module, since I've received pull requests (which I've been unable to effectively review), though I can't speak for them as to whether they'd be interested in maintaining the module. So, the module I want to migrate is _sort of "_abandoned", but, it was abandoned by me, and I'm not sure if I need to find someone else who wants to work with Vox Pupuli on it first, and transfer it to them, or what?

well what is it

and does it duplicate anything else

This message was deleted.

as for example a file and import it on multiple agents, so that all agents have the same file (provided they import the same resource)

i have a question, maybe someone has some ideas. currently a provider uses a command to generate the contents for a file during application to an agent, this involves some randomness so different files get generated for different agents. is there a way to generate the contents bevore they are stored in the puppetdb and then during application just take the data from there. basically i want to export some random generated file cont