It was decided that writing a JSON based pxp-module-puppet.conf
was a difficult proposition for the Windows MSI based on
that requiring a custom action. This would have been required
on Windows since Windows has the ability to relocate the
binary installation directory.
However, given that the pathing structure under the top-level
installation directory is fixed, we can use relative paths to
assume default values for the pxp-module-puppet "interpreter"
and "puppet_bin" configuration settings. The pxp-agent code
is being modified as such, and therefore the MSI no longer
needs to lay down a pxp-module-puppet.conf
Furthermore, on PE, a module will write the appropriate
configuration settings after initial contact with a master.
It was decided that writing a JSON based pxp-module-puppet.conf was a difficult proposition for the Windows MSI based on that requiring a custom action. This would have been required on Windows since Windows has the ability to relocate the binary installation directory.
However, given that the pathing structure under the top-level installation directory is fixed, we can use relative paths to assume default values for the pxp-module-puppet "interpreter" and "puppet_bin" configuration settings. The pxp-agent code is being modified as such, and therefore the MSI no longer needs to lay down a pxp-module-puppet.conf
Furthermore, on PE, a module will write the appropriate configuration settings after initial contact with a master.