-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> Hence, I would be glad if somebody could give me some hints of what >> might be the appropriate solution or at least where to look at the code >> and to understand the current concept. > > Well, there's a change_to_s method that you could override to provide > the right message.
Right, I also thought about that, but I hesitated as I saw that change more something like fixing the output than fixing the source of the problem. > My guess is that the default 'ensure' type is getting confused somehow > because it doesn't know what message it should use for 'purged'. Yes, this is also what I thought and if you think it's really only a matter of the output, then I'm doing something like that. > Lemme know if that doesn't work out. Will test and send a patch. > And I'm stoked to see someone's actually using this type. :) It fits really well into our setup and requires us to usually add not more than 3 lines (name, admin, password) for a new list :) thanks and cheers pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkvIGtUACgkQbwltcAfKi3+0OACfSTyRAvjO3JSz2nQVOy+rY7fW ZtQAnipJIOh9V+MVgoKZKkZPMk7smhoQ =rNdc -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
