---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Set up Ansible as a Day 1 task

# Set up Ansible as a Day 1 task {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Set up the Ansible console as a Day 1 task before running Discovery and deploying job templates.

## Before you begin

All
extra variables must have a variable called deploymentID. The value of this deploymentID is sent from the catalog request.

Select the Prompt on launch option next to the variables section in the template. This action allows you to update or override the default extra_vars with values from the catalog order form when launching the template.

Tag all resources with the deploymentID key to enable Discovery after provisioning.

Role required: admin

## Procedure

1. Save the extra variables in a JSON format locally, to discover and update Configuration Management Database (CMDB).
2. Create Ansible tower credentials to be used in Ansible Discovery.  
   For more information, see [Configure Ansible Tower user name and password](https://www.servicenow.com/docs/FbTW_eA72u0utyPSxUBzig "Configure Ansible Tower credentials to access the Ansible Automation Engine through your instance.").
3. Allow the extra variables and job templates to be overridden.  
   The default Ansible job template must be overridden for the pipeline to work with a Cloud Services Catalog Ansible automation catalog item.