Hi,
there might be ways to achieve this, but also plenty caveats.
You mention all of functions, resources and providers, but I see no
indication that all of them relate to your question. Are you aware of
the differences between the three?
Have you implemented anything already, or are you still in the interface
design phase?
Will Puppet do anything besides generating XML? Do you have any code to
do this already?
Thanks,
Felix
On 03/05/2015 03:22 PM, Nick Howes wrote:
> Hello,
>
> I am trying to define something that would let me do this, or
> something like it:
>
> fw_service { elasticsearch:
> ports => [ '9200-9300' ],
> zone => work,
> }
>
> fw_zone { work:
> source_addresses => [ '10.0.0.0/16' ]
> }
>
> And for the fw_zone resource to be able to enumerate data from
> services that declared that zone name. Since it end goal is generating
> XML I could always use the concat module to create concat::fragments
> in the fw_service resource, but I wondered if there was any other way
> of passing data between functions within a catalog run? Going into
> Ruby is fine and I'm using future parser so any Puppet 4 API specific
> stuff would be usable.
>
> Cheers
--
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/54F8D3B7.2080202%40Alumni.TU-Berlin.de.
For more options, visit https://groups.google.com/d/optout.
