Release r202619
What's new
This release contains the following new features:
Proxy: pull transport mode
The automator Proxy lets your packages securely reach systems inside your own network: a small application installed on one of your machines that executes predefined scripts or shell commands on behalf of your packages.
This release introduces the pull transport mode, which is now the default. The proxy opens every connection itself, from inside your network: it polls the automator for work over outbound HTTPS, executes each command locally, and posts the encrypted result back. No inbound firewall openings are needed, and internal systems are never exposed to the internet.
The proxy now also has its own documentation section, covering everything from getting started and installation to transport modes, execution modes, security and privacy, and high availability.
Other changes
This release contains a number of smaller changes:
- Outbound HTTP and Xurrent calls that are blocked by an AWS WAF challenge are now handled by the auto-retry mechanism.
- Fix: a package execution could hang when a Xurrent GET request unexpectedly returned an empty response. This was uncovered by the AWS WAF challenges mentioned above, which respond to a GET request with an empty body.
- The maximum duration of a package execution has been set to 4 hours. Executions that exceed this limit are aborted and marked as failed. See Maximum execution time. Based on an analysis of current execution times, this limit will most likely be reduced further in the future.
Timeline
The expected deployment dates for this release are:
| Environment | Date |
|---|---|
| Demo | Tuesday, July 28th |
| Production | Thursday, July 30th |
The deployment to the Production environment will be conducted outside of office hours (Central European Time Zone), usually between 8 and 10pm.