> Puppet manifests are declarative, not executable. This comes up frequently, and seems quite frustrating. People ask questions, and often are told their questions are wrong, because puppet is declarative. While it's sometimes correct, sometimes it's wrong. I'm pretty far from an expert, but I know I've had some my posts incorrectly branded as such. And a lot of things are easily transformed from one to the other.
I can't speak to the original poster's goal, but actually implementing something that lets me declare what the current state is, really does require testing what the current state is. Which, presumably, is why the exec type already supports "onlyif" and "unless". Extending those to other things doesn't seem crazy. And as it stands, several things I do basically come down to syntactic sugar around an exec. The first example that comes to mind "This machine should have a database named Foo" "...Oh, but only create it if it doesn't already exist, otherwise you'll just get spurious errors" Managing a bunch of modern software seems to boil down to process like that. seph --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Puppet Users" group. 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 -~----------~----~----~----~------~----~------~--~---