Note : Any tags associated with the playbook collection are upserted into the system when you import a playbook collection. To export a playbook collection, select the playbook collection and click Export. Any tags associated with a playbook collection are exported when you export a playbook collection.
To delete a playbook collection, select the playbook collection and click Delete. Users with Delete permissions on the Playbooks module can delete playbook collections. This message is shown since RBAC is enforced on playbooks, and this means that you can only see a listing of those playbooks for which you your team are the owner. As shown in the above image, The Demo collection shows that 3 playbooks are part of the collection.
You can also search for a playbook by typing keywords in the Search textbox. Click the More Options icon to export records from the playbooks listing view in the csv or pdf format. You can also reset the playbook record fields to the default fields specified for the playbook module, click the Reset Columns To Default option. The playbook must be in an appropriate JSON format.
Any tags associated with the playbook are upserted into the system when you import a playbook. Follow the same process as specified for the Playbook Collection import and the same restrictions as applies to the Playbook Collection import applies to the Playbook import. Any tags associated with a playbook are exported when you export a playbook. You might clone playbooks if you want to reuse the playbook as a starting point for a new playbook. Cloning the playbook clones every step within the playbook.
You can select more than one playbook to clone at a single time. Once you clone a playbook, you can edit it as per your requirements. Clicking Select in the Move to collection section displays the Collection dialog. From the Collection dialog, select the collection to which you want to move the playbook and click Submit.
To delete a playbook, select a playbook and click Delete. Users with Delete permissions on the Playbooks module can delete playbooks. In the Playbook Designer , you can configure the following for the playbook: Change the state of the playbook by clicking the Is Active box, for example, change the state of the playbook from Active to Inactive.
Change the Name of the playbook, by clicking the name box and updating the name. You can also add or update the Description of the playbook, or add or remove Tags from the playbook. Modify the trigger for the playbook, change or add steps or actions to the playbook.
Use the Tools menu to enhance your playbook: To add parameters, use the Edit Parameters option. To add global variables, use the Global Variables option. To view the execution history of the playbook, use the Execution History option. For more information see the Debugging and Optimizing Playbooks chapter. To change the execution priority for a playbook, use the Execution Priority option.
For more details, see the Changing the prioritization of playbook execution section. You can thereby check the validity of the jinja and the output before you add the jinja to the playbook.
For more information, see the Dynamic Values chapter. Optional Other actions that you can perform in the playbook designer are: Use the Export button to export the playbook in the JSON format. Use the Delete button to delete the playbook. For more details, see the Playbook Debugging - Triggering and testing playbooks from the Designer section.
Version 7. When you perform bulk operations such as moving, cloning, or deleting a number of steps in one go, clicking Undo reverts the step modification.
Similarly, if you have modified a step and saved it, clicking Undo , reverts the step modifications. Also, note that if you have made multiple changes in a small time period around a second , then all these small changes are considered as a single operation. Once you have completed updating the playbook, click Save Playbook. You can drag and drop multiple selected steps. Ensure that you have clicked on your playbook canvas to bring it in focus before you copy the step s.
Note : The trigger step will not be copied. Ensure that you have clicked on your playbook canvas to bring it in focus before you paste the step s. Note : You can also select Paste from the Edit menu in your browser to paste the copied steps. You can delete a step or multiple steps by selecting steps and pressing the backspace or the delete button.
You can use the Auto-Align - Vertical and Auto-Align - Horizontal buttons to align the playbook vertically or horizontally. You can use these buttons to make your playbook look neat and organized, which is especially useful for very large playbooks where playbook readability might be an issue.
Playbook Debugging - Triggering and testing playbooks from the Designer From version 6. Changing the prioritization of playbook execution From version 6. Playbook execution prioritization works as follows: If any worker is available for the task execution, it gets assigned a task from the "High" queue first and so on. If all workers are occupied with lower priority tasks and any higher priority task comes up, the high priority task gets executed only when any worker is again available.
Low priority tasks do not get executed if there are high priority tasks. Notes : All 'sync' reference playbooks automatically inherit the priority of their parent playbooks, thereby ignoring any preset priority. If you update the execution priority of a scheduled playbook, then you require to edit and resave the schedules associated with that playbook. If you want to schedule a data ingestion playbook, then you must set the priority of the data ingestion playbook before scheduling the same.
Live User implementation in Playbook Designer The playbook designer implements Live Users, which means that the playbook designer displays users who are also currently working on the same playbook. Live Users has the following benefits: Users are notified of other users or sessions that are active on the same playbook.
Users work on the latest version of the playbook, and they do not lose their updates made to the playbook. Saving versions of your playbook You can save versions of a playbook that you are creating or updating. To take a snapshot and revert the playbook to a particular snapshot do the following: In the playbook in which you are working in the playbook designer, click Save Version.
In the Save Version dialog, add a note that you want to associate with the version and click Save Version. It is recommended that you add meaningful notes for versions as these names will help you in identifying the snapshots when you want to revert to a particular version.
Once you click Load , that snapshot is loaded in the playbook designer, with a message: "You are working on a previously taken playbook snapshot Exporting versions of your playbook From version 6. Retaining the versions of playbooks while exporting playbooks enables you to load a snapshot of a previously saved version of the playbook into an imported playbook You can choose to export playbook collections or playbooks with saved versions of the playbooks as shown in the following image: Clicking Yes, include versions on the above dialog will export playbooks or playbook collections with the saved versions of the playbook.
This opens the Versions dialog as shown in the following image: You can load a snapshot of a previously saved version of playbook in the Versions dialog by selecting the snapshot that you want to load in the playbook designer and clicking Load. Playbook recovery FortiSOAR autosaves playbooks so that you can recover playbook drafts in cases where you accidentally close your browser or face any issues while working on a playbook.
To recover an unsaved draft of the playbook, reopen that playbook in the playbook designer you will be prompted to confirm whether you want to recover the draft of the playbook as shown in the following image: Once you click Confirm on the Confirm dialog, the autosaved version of the playbook is loaded in the playbook designer, and you can then choose to save this playbook using Save Playbook and make it the current working copy.
System Playbooks FortiSOAR includes some system playbook collections that are used to automate tasks, such as the Escalate playbook which is used to escalate an alert to an incident based on specific inputs from the user and linking the alert s to the newly created incident.
You can also reference the Escalate system playbook from other playbooks. You can modify system playbooks as per your requirements. To ensure that the correct hostname is displayed in the email, you must update the appropriate hostname as per your FortiSOAR instance, in the playbook, using the Playbook Designer as follows: Open the Playbook Designer.
You can optionally specify a default hostname value in the Default Value field. Click Submit. This adds the updated hostname for your incident and then when a system playbook sends an email the link contains the correct hostname.
When an alert record is assigned to a user, then FortiSOAR auto-populates the Assigned Date field in the alert record, with either today's date or the date on which the record was assigned. These Plays help you build great agile teams. Sort through what you learned, loved, loathed, and longed for in the past quarter. Keep the team informed, connected, and calibrated through this regular ritual. Close View this page in your language? All languages Choose your language. Open and close the navigation menu.
Team Playbook Open and close the navigation menu. Build strong teams with Plays. Explore Plays. One or more Ansible tasks can be combined to make a play. Two or more plays can be combined to create an Ansible playbook. Ansible playbooks are lists of tasks that automatically execute against hosts. Groups of hosts form your Ansible inventory. Each module within an Ansible playbook performs a specific task. Each module contains metadata that determines when and where a task is executed, as well as which user executes it.
There are thousands of other Ansible modules that perform all kinds of IT tasks, such as:. Ansible is capable of communicating with many different device classifications, from cloud-based REST APIs , to Linux and Windows systems, networking hardware, and much more.
This is a sample of 2 Ansible modules automatically updating 2 types of servers:. Ansible uses the YAML syntax. There are also 2 different, but perfectly acceptable, YAML file extensions:. After installing the open source Ansible project or Red Hat Ansible Automation Platform which is as straightforward as typing sudo yum install ansible in the Red Hat Enterprise Linux CLI , all you need to do is use the ansible-playbook command to run Ansible playbooks.
The Red Hat Ansible Automation Platform web-based user interface includes push-button Ansible playbook deployments that are used as part of larger jobs or job templates. These deployments come with additional safeguards that are particularly helpful to users who are newer to IT automation—or those without as much experience working in the CLI.
Sign up for our free newsletter, Red Hat Shares. Open hybrid cloud Support Developers Partners Start a trial.
0コメント