On Friday, December 26, 2014 3:40:07 AM UTC-6, [email protected] wrote:
> ---In my setup, there are two applications (applnA and applnB) running on > the same host. My requirement is to configure applnB. > The configuration values are input to UI and the UI is part of applnA > only. > > If the application providing the configuration GUI runs on the same machine as the application being configured, then why do you want to put Puppet between? The only thing I'm coming up with is to revert changes to application B's configuration that are not made via the GUI. If that's not a significant concern then application A should just configure application B directly. It will be no harder to code that than to make Puppet do the job, especially given that you are starting from zero with Puppet. There are many advantages to such direct coupling if you can rely on the applications running on the same host. If you do want to get Puppet involved, then the GUI program needs to record the configuration data on disk (somewhere other than the target application's config files). To get that data into Puppet, you could write an ENC, you could use hiera (possibly requiring you to write a custom back-end), or you could write custom parser functions. In any case you will write Puppet classes and/or defined types modeling the target application's configuration in terms of the data involved (Puppet has rich facilities for this part). I apologize for speaking in generalities, but you haven't provided any specifics for us to work with. John -- 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/aad7e327-4c9c-4ada-ab4d-06b7f029adbc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
