[Puppet Users] Re: removing resources no longer specified

[Udo Waechter]

Hi.




Usually we have something like:

class foo {
        $presence_real = $presence {
        "" => "present',
        "absent" => "absent"
        }
        file{"xyz":
        ensure => $presence_real,
        }
        package{"a_package":
        ensure => $presence_real
        }
        case $presence_real {
                "present": {
                        exec{"echo 'hello world' >/tmp/hello":
                        onlyif => "test ! -e /tmp/hello",
                        }       
                }
                "absent": {
                        file{"/tmp/hello":
                        ensure => $presence_real,
                        }
                }
        }       
        # and so on
}

class foo::none {
        $presence = "absent"
        include foo
}







include foo::none



include foo { ensure => "absent" }



Bye,
udo.

On 15.06.2009, at 01:27, Geoff Crompton wrote:

We also do this for most of our classes and it increases the code that has to be written. This works pretty well, but there is a lot of redundant code within all of our classes now. In the last days I got the idea that it might be nice if puppet would create these 'anti' classes by itself all resources in "class foo" that have an ensure parameter could be set to "absent" when the class is referenced via: The other option would be to introduce arguments to classes. I think this is a feature request already. Of course this would not solve the problem for all types ("exec" is hard...), but it is a good start. And it would save a lot of code already.

Currently, if I want to remove resources from a node that I've
previously configured, I'm doing 'anti' patterns. Is there away for
puppet to do it for me? For example, if I started with:

define website () {
    file { "/etc/apache2/sites-enabled/$name.conf":
        content => template("website/apache2.conf.erb")
    }
}
node 'oldwebserver' {
    package { apache2:
        ensure => installed,
    }
    website { "www.example.com":
    }
}

And then I wanted to get ride of that website from that specific node:

define website::anti () {
    file { "/etc/apache2/sites-enabled/$name.conf":
        ensure => absent
    }
}
node 'oldwebserver' {
    package { apache2:
        ensure => absent,
    }
    website::anti { "www.example.com":
    }
}


node 'oldwebserver' {
}


Package and File resources in their last configured state, and forgets
about them. So I was wondering if it is possible for a storeconfigs
database to store some history of configs?


possible with that history to determine when a resource changes from
existing in the manifest, to not existing in the manifest?

If that is possible (or could be built in), could you make puppet

a resource has been removed?

--
+-Geoff Crompton
+--Debian System Administrator
+---Trinity College

--~--~---------~--~----~------------~-------~--~----~

To post to this group, send email to puppet-users@googlegroups.com
To unsubscribe from this group, send email to 
puppet-users+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---

But can puppet make this easier for me? What I'd like to do instead is: At the moment puppet doesn't behave in that manner, it simply leaves the If it is possible (or if it's possible to build that feature in), is it automatically remove that resource from the client system if it detects You received this message because you are subscribed to the Google Groups "Puppet Users" group.

--
:: udo waechter - r...@zoide.net :: N 52º16'30.5" E 8º3'10.1"
:: genuine input for your ears: http://auriculabovinari.de
::                          your eyes: http://ezag.zoide.net
::                          your brain: http://zoide.net

smime.p7s
Description: S/MIME cryptographic signature