It seems to me that you will be relinquishing puppet's ability to maintain the
content of the file by doing this. If that's acceptable, use the replace
parameter to only have puppet maintain the initial config and allow the file to
be changed outside puppet moving forward. If that's not acceptable, then the
location from which the template values are derived must be updated in
lock-step with the changes you make externally to puppet. This may be possible
programmatically depending on your scenario, but it feels like the wrong
direction to go to me.
I might approach this with a wrapper class that has awareness of resource A and
resource B, and feeds them both the proper parameters to satiate their needs
when cohabitating.
Alternatively, I might stub out a conf.d style config directory and provide to
resource B a handle into resource A's config file through an included config
file owned by resource B.
=MobileMail=
Please excuse brevity or spelling errors
On May 20, 2013, at 11:39, Schofield <dbschofi...@gmail.com> wrote:
> Given a configuration file that is initially managed by a template in File
> resource A . Resource B interacts with a middleware product through its
> published admin API which causes changes within File resource A. Is there
> anyway, through custom provider code for resource B to tell resource A that
> its changes affect the configuration file so that when the state of resource
> A is checked it accounts for the changes made by B?
> --
> 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?hl=en.
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
--
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?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.
