Re: [Puppet Users] Metaparams break rake tests - how to avoid it ?

> On 27 Oct 2016, at 02:35, Jakov Sosic wrote: > > On 10/22/2016 04:32 PM, Martin Alfke wrote: > >> This code is fine. >> You just declare a stage resource type. >> Except for: why do you want to make use of stages? >> Stages have been introduced as a high level ordering

Re: [Puppet Users] Metaparams break rake tests - how to avoid it ?

I believe what Martin was saying is, try `$stage_name` instead of `$stage` (or similar), because `$stage_name` would not be a reserved word/metaparameter name. Rob Nelson rnels...@gmail.com On Wed, Oct 26, 2016 at 8:35 PM, Jakov Sosic wrote: > On 10/22/2016 04:32 PM, Martin

Re: [Puppet Users] Metaparams break rake tests - how to avoid it ?

On 10/22/2016 04:32 PM, Martin Alfke wrote: This code is fine. You just declare a stage resource type. Except for: why do you want to make use of stages? Stages have been introduced as a high level ordering concept which is no longer best practice. You should use standard ordering instead

Re: [Puppet Users] Metaparams break rake tests - how to avoid it ?

Hi Jakov, > On 15 Oct 2016, at 05:18, Jakov Sosic wrote: > > Is there a way to disable metaparam checks, so that it won't break CI for my > module? > > I have something along these lines: > > my/manifests/init.pp: > class my { > stage {'mystage': before => Stage['main'] }

[Puppet Users] Metaparams break rake tests - how to avoid it ?

Is there a way to disable metaparam checks, so that it won't break CI for my module? I have something along these lines: my/manifests/init.pp: class my { stage {'mystage': before => Stage['main'] } } my/manifests/conf.pp: class my::conf ( $stage = 'mystage', ) { ... } So, when I run: