Module Version: 1.6.0
Puppet Version: 5.3.5 (PE 2017.3.5)
OS Name/Version: RHEL 7 (Server) Solaris 10 (Agent)
Describe your issue in as much detail as possible...
Desired Behavior: Do not start the puppet agent after upgrading, or at least give the option when doing a Solaris 10 agent upgrade.
Actual Behavior: The /tmp/solaris_install.sh script generated by the puppet_agent class hardcodes the startup/enable of the "puppet" and "mcollective" services regardless of the value of puppet_agent::services or puppet_agent::install_options, or the settings I have in my puppet.conf (most notably agent:daemonize=false)
We do not run puppet as an agent and this unexpected behavior has caused us problems.
Please take a moment and attach any relevant log output and/or manifests. This will help us immensely when troubleshooting the issue.