Version 102 of the HTTP Action Type PowerPack includes a new custom action type and a new automation policy. It also includes several updates to the "Make an HTTP Request" action type.
- Minimum Required SL1 Version: 8.10.0
Version 101 of the HTTP Action Type PowerPack was not released as a general availability PowerPack. This document describes all of the changes from version 100 to version 102.
Before You Install or Upgrade
Ensure that you are running version 8.10.0 or later of SL1 before installing " HTTP Action Type" PowerPack version 102.
For details on upgrading SL1, see the relevant SL1 Platform Release Notes.
Installation or Upgrade Process
To install version 102 of the HTTP Action Type PowerPack, perform the following steps:
- See the Before You Install or Upgrade section. If you have not done so already, upgrade your system to the 8.10.0 or later release.
- Familiarize yourself with the Known Issues for this release.
- Download the HTTP Action Type version 102 PowerPack to a local computer.
- Go to the PowerPack Manager page (System > Manage > PowerPacks). Click the menu and choose Import PowerPack. Import the HTTP Action Type version 102 PowerPack. For details on importing PowerPacks, see the chapter on Installing a PowerPack in the PowerPacks manual.
- Click the Installing a PowerPack in the PowerPacks manual. button. For details on installing PowerPacks, see the chapter on
- See the Run Book Automation manual for instructions on using Action Type contained in the new PowerPack.
Features
This release includes the following features:
-
Includes the following action types, which can be used to build an automation that performs an HTTP request and formats the response:
- Make an HTTP Request
- Format HTTP Action Output
-
Includes an automation action, "Datacenter Automation: Basic JSON Output Formatter". This automation action can be used to apply simple HTML formatting to API requests where the response is in JSON format.
This PowerPack does not include automation policies.
Enhancements and Issues Addressed
The following enhancements and addressed issues are included this release of the " HTTP Action Type":
- The dynapp_guid parameter in the "Make an HTTP Request" action type is now used to check for an aligned credential on the root device of the associated device.
- A new custom action type, "Format HTTP Action Output", has been added to the PowerPack. This action type can be used to create an automation action that formats the output from automation actions that use the "Make an HTTP Request" action type using a Jinja template.
- A new automation action, "Datacenter Automation: Basic JSON Output Formatter", has been added to the PowerPack. This automation action uses the "Format HTTP Action Output" custom action type. This automation action can be used to apply simple HTML formatting to API requests where the response is in JSON format.
- When an automation action that uses the "Make an HTTP Request" action type receives a response with a non-200 error code, the response body is now included in the error message.
- To work around an issue where automation actions are not providing the associated device name in the correct case, the HTTP action type now looks up the device name before processing substitution characters.
- Substitution characters are now correctly processed for the "payload" and "relative_url" parameters of the "Make an HTTP Request" custom action type.
- When a POST request is specified in the credential for an automation action that uses the "Make an HTTP Request" custom action type, the payload is now sent correctly in the request.
Known Issues
This release has no known issues.