Containerized private minion (CPM) release notesRSS

Improvements

• Updated Runner image dependencies to remediate high severity CVE (Common Vulnerabilities and Exposures).

Fixes

• Secure Credentials are now masked in navigation timing section of the HAR file.

Changes

• Scripted API and Scripted Browser monitors no longer fail based on response codes.
  • Before this change, a scripted API/Browser monitor would fail if the first request returned an Error response code (4xx/5xx). However the script would not fail if any subsequent request returned a failed response code.
  • If you would like to fail on response code, please use asserts.

Fixes

• Fix secure credential sanitization in scripted monitors.

Improvements

• Users now have access to the NPM module ssl-checker for scripted monitors.

Improvements

• Improves error processing for Synthetic step monitors

Fixes

• Changed permissions to correctly include restricted deletion flag
• Allows setting Selenium timeouts to a value of 0 for ScriptTimeout, ImplicitTimeout, and PageLoadTimeout

Fixes

• Fixed issue where $browser.findElement(...) was not returning a WebElementPromise.

Known Issues

• Users cannot disable implicit timeouts. Setting Implicit Timeout to 0 causes the implicit timeout to be set to JobTimeout (180s for Public Minions).

Improvements

• Selenium Timeouts such as PageLoad, Implicit, and Script are managed to ensure jobs can't exceed the JobTimeout.

Fixes

• Fixed Issue where a job that's already gracefully shutting down could hit the JobTimeout and terminate shutdown tasks.

Known Issues

• Users cannot disable implicit timeouts. Setting Implicit Timeout to 0 causes the implicit timeout to be set to JobTimeout (180s for Public Minions).
• $browser.findElement(...) does not return a WebElementPromise. Meaning users cannot use methods such as .click() or .sendKeys(...) directly on the findElement method.