> You might consider using create_resources with hiera. Here's a simple
> example.
>
> yaml data
> ---
> apache::a2mods:
> expires: {}
> gnutls: {}
> headers: {}
> rewrite: {}
> apache::vhosts:
> statsstage.example.com:
> priority: '99'
> a_template: 'apache/vhosts/stats.example.com.erb'
> stage.example.com:
> priority: '00'
>
> And the class the queries Hiera and pumps the data through various
> defines.
>
> class profile::apache {
>
> include ::apache
> include logrotate::apache
>
> $mymods = hiera('apache::a2mods', {})
> create_resources('apache::a2mod', $mymods)
>
> $myvhosts = hiera('apache::vhosts', {})
> create_resources('apache::vhost', $myvhosts)
>
> }
>
> Ramin
>
Thanks for your answer.
In your example using hiera, you put all vhosts config data in one yaml
file. This solution seems to be maintainable in this case but if I use this
solution for bind::zone datas the yaml file still be very big and difficult
to maintain.
Is it possible with hiera to split this config data in multiple files which
contain each bind::zone resource for example?
Regards,
Thomas
--
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 post to this group, send email to puppet-users@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.
