Kyndryl Bridge

Experience Kyndryl Bridge

Expand menu Collapse menu

Create an action using Ansible Tower

Published On Jul 18, 2024 - 1:25 PM

Create an action using Ansible Tower

Explains how to create actions in CAS using Ansible Tower actions.

To enable the action in the user interface, make sure to include the following properties:

Name	Description
actionConfigPara	This flag must be set to true if the user configuration is defined in a separate file than the action definition.
actionDefinitionId	Specify definition id required for action. This should be unique across actions.
actionDefinitionVersion	The version is used for the action definition. The current version should be 2.0.0.0
actionDefinitionDisplayLabel	Specify Label as per action. For example: "Power On vm"
actionType	Specify the action type: provisionNew stateChange configChange deprovision
associatedTo	Specify the resource type and pre requisites for each subscription.
Modern Operations applications	Specify the subscription you will use. For AIOps, use "aiops:service". For EM, use "consume:service".
provider	Define the provider for the action. contentProvider: Specify contentProvider as github in every action-definition. manageProvider: Optional, default it to targetProvider fulfillmentProvider: Specify external provider for fulfillment purpose code like tower targetProvider: Specify cloud provider code as targetProvider like aws / gcp / azure / ibm
routingKey	Specify as 'engine'.
status	Status for this action. Set as published.
actionDefintionRetriableTTL	It should be as "1440".
isRetriable	This flag should be set to true.

The integration template allows you to perform an action.

Name	Description
_configInfo	The user selected values are available if a configuration is linked to the definition template.
_resourceInfo	Passed by respective application from where action is invoked.
_targetProvider	Target provider account details.

Do you have two minutes for a quick survey?