Ups! Sorry Felix!! :P I think there is a resource needed exec when the code shows that there is a parameter for the --force-yes. Anyway it is true that there is very little documentation on the official website of puppet, if someone could give me some place where there is more information I would appreciate that. Felix, thank you very much for everything, I will consider your advice if i finally do not get more information.
Regards and apologies for the error in the name before! : P P.S: And sorry for the english, i use google translator :P On 13 ene, 10:22, Felix Frank <felix.fr...@alumni.tu-berlin.de> wrote: > On 01/13/2012 09:31 AM, Antonio Xanxess wrote: > > > Hi Frank, > > Actually it's Felix :) > > > Thanks for the reply, but in principle I think that there is no need > > for this procedure because the resource itself package can do, besides > > not a good practice to patch existing functionality. > > Uhm, what? o_O > > You talk about savaging the apt provider code to somehow include > --force-yes into the apt-get options, then point out how patching > existing functionality is bad practice? Huh. > > Frankly, pushing a hacked apt provider to all your agents will be much > more invasive than falling back to a manifest-based workaround. > > Regards, > Felix -- 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.
