On Wednesday, March 12, 2014 9:27:24 AM UTC-4, jcbollinger wrote: > > > > On Tuesday, March 11, 2014 7:08:45 AM UTC-5, Mark deJong wrote: >> >> >> I'm having the issue with the passwd::user accepting the schedule >> metaparameter. I have tried it both with and without define the variable >> 'schedule.' >> >> > > The thing that jumps out at me right away is that you are declaring your > own $schedule parameter to your class and defined type. All Puppet classes > and resource types, including defined types, have that [meta]parameter > automatically, without you declaring it. It may be that by declaring it > explicitly you are shadowing the metaparameter with an ordinary parameter > of the same name. > > I thought that initially as well, and had tested removing my declared $schedule previously. Just to be sure I have removed all references of my own 'schedule' parameter again and it still yields the same results. I'll try to reproduce the bug report referenced by Felix.Frank.
> Additionally, > > - class passwd::schedule should not inherit from class passwd. It > yields no benefit whatsoever for the code presented, and it creates a > circular evaluation dependency involving those two classes (which Puppet > nevertheless seems to handle successfully). > - a schedule has no effect of its own on catalog application, > therefore it is useless (but also harmless) to include class > passwd::schedule in your relationship chain. It would be sufficient to > just declare it without chaining. > > Thanks for the additional feedback! ;) > > John > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/65122374-68f5-42c5-baca-23a277ecce01%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
