Displaying 1 result from an estimated 1 matches for "remove_a".
Did you mean:
remove_at
2007 Jul 05
1
Groping for a design pattern on negative configuration elements.
...h
that the system is not burdened with a ton of extra overhead checking
for things that don''t exist?
B) How should this be done anyway?
My gut reaction is to have something like the following:
class A {
define install_A {
file { "foo": ensure => present }
}
define remove_A {
file { "foo": ensure => present }
}
}
Then call remove_A in all cases where you don''t want to have ''foo'' present.
But....technically, this only needs to be successfully called once and
I don''t want to spend the cycles checking for the exist...