While this sounds like a good idea, I would argue that it breaks the
principle of leas surprise.
If I assign a module to a server I would expect that module to do what it
is intended to do. If it can't do that and it doesn't tell me that it can't
do that then I may assume that the module has done it's work and the server
is OK when that isn't actually the case.
You can declare your modules only where they are functional. Instead of
putting them in common.yaml configure hiera to look for ${kernel}.yaml or
${lsbrelease}.yaml and declare your module only in the places where it
works.
On Fri, Oct 10, 2014 at 7:28 AM, jmp242 <[email protected]> wrote:
> I may be doing something really stupid per Felix.Frank, but we decided to
> make all our modules have:
>
> Case $kernel {
>
> 'linux': {
>
> }
>
> 'windows'{
>
> }
>
> }
>
> form... It seems to work well for us?
>
> --
> 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 [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-users/4c143008-659a-416e-aaa1-6fd3a43e931c%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-users/4c143008-659a-416e-aaa1-6fd3a43e931c%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Perfection is just a word I use occasionally with mustard.
--Atom Powers--
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/CAF-H%3DOkteeXnWecOhhYAeXFpxeF8bLWanWGCb1gW1FAjXdx5rw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
