(MODULES-9798) Add Timeout Parameter for the Current Puppet Run

[phil4business]

• (Support-42796) Add wait_for_puppet_run parameter to configure the timeout value for the current puppet run.
  Previously, if the puppet agent was to be upgraded but the current run took longer than 120000 ms (2 minutes) to complete, the agent upgrade script (install_puppet.ps1) would fail. This would happen even if the agent run would have otherwise completed without error.

• Fixed wait_for_pxp_agent_exit parameter tests. The parameter accepts an Int32, but the tests were passing booleans.

[puppet-community-rangefinder]

puppet_agent is a class

that may have no external impact to Forge modules.

puppet_agent::install::windows is a class

that may have no external impact to Forge modules.

This module is declared in 3 of 576 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.

[CLAassistant]

All committers have signed the CLA.

[GabrielNagy]

Hi @phil4business, thanks for your contribution! 🎉

The PR looks good, good catch on the spec tests. Also, we really appreciate the effort to keep the documentation up-to-date.

I found a JIRA ticket that relates to this: https://tickets.puppetlabs.com/browse/MODULES-9798

To get PR checks to pass, can you squash your commits and prepend the ticket ID to your commit? Something like (MODULES-9798) Add Timeout Parameter for the Current Puppet Run. Let me know if you need any help with this.