Onboarding by discovery

actions discovery allows you to import content and create your own actions from two sources and also ansible tower select this option to create actions from scratch for playbooks discovered in a github or ansible tower account the main benefit of actions discovery is that it enables you to bring your personalized action content available in your sources, such as github or ansible tower using the user interface (ui) this makes the discovery of action content automatically and onboards the actions into the kyndryl modern operations applications very quickly prerequisites the following permissions are needed to be able to discover and onboard actions the actions registry admin action role is the only role that includes all these permissions the platform administrator can create custom roles and assign them the permissions needed to discover and onboard actions \<font color="#f3f4f6">permission\</font> \<font color="#f3f4f6">description\</font> actions action types crud allow to perform crud operation on action types actions action onboarding crud allow to perform crud operation on action onboarding actions action definition view allow to perform view operation on action definition actions action definition crud allow to perform crud operation on action definition actions action policy view allow to perform view operation on action policy the onboarding process is divided into four steps step 1 select content sources from the actions admin page, click the onboard action+ button select the following import option onboard by discovery click ok a new page is displayed select one of the following source types github or ansible tower select the source account to discover your actions from the dropdown list add the content technology from the dropdown list different content sources are displayed based on the source account selected to look for a specific content source, use the search bar for github check the box next to the content name a maximum of five sources can be selected for ansible tower select workflow or template click the select and continue button the discovery process initiates you can wait for the discovery to finish or select to go to the actions admin page step 2 discover and select actions once the discovery process is completed and successful, a tree structure opens select the action files that need to be onboarded click save and continue step 3 (optional) bulk assign actions select one or more actions to assign to a target provider you can select multiple actions at once for a more expedited process however, only one provider can be assigned to those actions click bulk assign , select the target provider to be assigned, and click continue step 4 onboard actions you are presented with a summary of the actions to be onboarded and the target provider for each of them click save and continue to start the onboarding process publishing onboarded actions to publish your recently discovered actions, follow these steps edit the action definition select the action that you want to onboard and click the overflow menu select details the details page opens click edit details make the necessary edits to the action's details and save the changes the details page shows the following fields for you to update, if needed action definition id id used for linking actions files action definition display label label shown to the user on the application side action type select config change if you need the user to enter some data to execute the action otherwise, classify your action as state change, deprovision or provision new description a brief description of what this action is for actions template a template containing key information for the execution of the template for example, the link between resource information and the playbook variables for more information, click the information icon associated with resource family resource families where this action is shown context scope for action execution application application where the user can run this action from content provider usually the content source target provider cloud provider where the action is performed fulfillment provider tool provider in charge of execution add an action configuration when action type has been set to config change , the actions requires some input from the user to configure these inputs, click manage configuration remember to save any other changes made to the details page before going to the manage configuration page add the configuration name of your choice you can add as many configurations as inputs are required from the user click view more in each of the configuration ids added to make the required configuration updates config id and binding usually take the same value this value is linked to the playbook through the action template for input type select free text to display an input box where the user can enter any text select single select to display a dropdown menu where the user can select only one choice select multi select to display a dropdown menu where the user can select more than one choice for description this is a help text displayed so the user knows important information about that input for validation this is a regex expression used to validate the user input if validation fails, then whatever is in the error message text box is shown validate action data once the configuration details are complete, click validate to check if the information provided is correct publish action to publish your action, from the actions admin page, follow one of these three options click the overflow menu for the action you want to publish and select validate & publish select the checkbox for multiple actions that you want to publish and click validate & publish on the top of the table go to the actions details page for the action that you want to publish and click publish at the bottom of that page executing discovered actions your discovered actions must be visible for the respective resource families once they are published in this way, you can execute that action as previously explained troubleshooting in case of error during the execution time, check the action definition and configuration for any mistakes editing published actions is not supported yet if you are unable to fix any errors, start a new discovery process and fill all data from scratch