similar to: purging unmanaged cron

We have resources that, from time to time, are selected to be removed (unmanaged). When it comes to ssh keys, fstab... this leaves a lot of stuff behind that we don''t want. Is there a simple way to remove the unmanaged data so we can keep the systems clean. Thanks. -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post

http://projects.puppetlabs.com/issues/7600 I call this the "agent orange" option :) This works, purging all unmanaged hosts entries: resources { ''host'': purge => true, noop => true, } We should have a similar property for all (most?) types. Please comment on the ticket or reply here, whichever you prefer. Thanks! r P.S. This is in

I attempted the following: resources { service: purge => true, noop => true } service { sshd: ensure => running; iptables ensure => running; } And got the following message: notice: Starting configuration run err: Found a bug: uninitialized constant Parse notice: Finished configuration run in 0.47 seconds When I remove the ''resources'' line, everything works

Hi all, I''m using the opsview module and the Opsviewmonitored type and it''s working just fine, I''m now trying to purge unused hosts from the Opsview monitoring (I have several hosts that dynamically go up and down). The problem is that it seems like the destroy function for opsview was not really implemented and therefore I can''t really delete hosts from

I have a little issue with purging. I use: file { [''/etc/shorewall/puppet'',''/etc/shorewall/puppet/rules'']: ensure => directory, mode => 0700, recurse => true, purge => true, } but purging does not work, i can do a touch

I have a situation where I''d like to perform some actions when a node is removed from a class. I have a few (homegrown) services that install ssh keys in authorized_keys and it''s possible that a node may have the service enabled and disabled during it''s lifetime. When disabled I''d like to clean up the ssh keys for security reasons. This brings up the broader

I''m not sure if this has been posted previously, but I couldn''t find any information on it. I added a cron job via the cron type and it installed properly. Next, I removed the cron type from the manifest. The result was that, while the entry was no longer in the yaml file, the cron entry was not removed! Is this a bug, or the way that it is supposed to function? Thank you,

Hi All, is it possible to delete cronjobs by patterns using ''cron'' resource? I.e. I want to make sure that there is no any cronjob that contains "/ path/to/some/unneeded_file" command in root crontab without knowing the command possible parameters and schedule. If no, any suggestions about how it can be performed are welcome. Thanks in advance

So I have the following: define nagios::service ( $nagios_template = ''service-template'', $host_name = $fqdn, $service_groups = '''', $contact_groups = $default_contact_group, $max_check_attempts = 3, $dependency = false, $dependent_host = $fqdn, $dependent_service = '''', $check_command = '''' ) {

Is there a way to exec something on purge?

Hello Does anybody share how to roll-back configuration if puppet definition on host is change. For example Let''s assume we have host on which initial was web server and bunch of users. All this resources we configured throw puppet. node <some node> { <webserver difinition> <user1 definition> <user2 definition> <user3 definition> } At some

I would like to write up brief tutorial/documentation on how to manage /etc/passwd using puppet. While this may seem pretty straight forward to some...the documentation is not. We have been able to create a manifest that defines all of our users "virtually" and are able to "realize" users and add them to the system(s) running puppetd. Is there a way to simply realize all users

I have the following define... define puppet::module_dir { if $name { include puppet file { "${puppetdir}/modules/${name}": ensure => directory, mode => 0755, purge => true, recurse => true, } } } I call it like so: puppet::module_dir { "main" } puppet::module_dir

Hi All, I asked on IRC but didn''t have everything organized and most people seemed busy. Hoping someone can see what I''m missing here. I''m trying to create a network module, used similar to the ''users'' configuration described in the Best Practices document. I have a users module which has that and it works with similar syntax to below. If I

Hello all, The key issue is, if I uncomment the line: Myresource <<| |>> { ensure => present } I get the error: err: Could not find type Myresource on node hmaster I''m attempting to follow the instructions from the book Pro Puppet pgs. 143-145; however, it seems that there''s a parser issue or I''m very lost, as I am unable to export and collect my

Ok, given the statement on the web page about unlesssystemuser under Resources ( http://reductivelabs.com/projects/puppet/documentation/typedocs.html#resources), I assume that users can be purged. However, when I attempt to do this with resources { user: purge => true, noop => true } and what I get is: err: Found a bug: private method ''split'' called for nil:NilClass.

But is that not adviced in the manual[1]? I am also in the process of setting up dovecot behind a haproxy. Still testing with this. I was wondering why one would choose haproxy and not eg dovecot proxy (with director) [1] https://wiki2.dovecot.org/HAProxy -----Original Message----- From: Zelic Bojan [mailto:bojan.zelic at kudelskisecurity.com] Sent: woensdag 26 augustus 2020 23:39 To:

Hi, We''re using thin stored configs heavily to manage things like Munin and Nagios and we''re currently wondering what to do when nodes go away, or change considerably. If we get rid of a server then all it''s stored config is still present in the database, as well as it''s nagios and munin configurations. We created a script that iterates through the database

Hello, I'm facing an issue where deleted emails keep re-appearing after my mailbox index gets recreated.??I'm running version 2.2.36 of dovecot, but I tested the same scenario under 2.3.10. I'm also using mdbox, autoexpunge, and using dovecot replication. I've had several instances now where some expunged emails show up again in a mailbox. I noticed this error: doveadm: Error:

Hi all, Please excuse me if someone has already offered this, but I think the Apt provider should, in addition to -y and -q, also do --purge. This will remove config files and keeps /etc cleaner on the whole. Just a suggestion. Great product and keep up the good work etc. -- Gegroet, Tim (tim|mac or tim|imac on irc)