#FINALE INVENTORY ENABLE CONNECTION INSTALL#
#FINALE INVENTORY ENABLE CONNECTION UPDATE#
#FINALE INVENTORY ENABLE CONNECTION TRIAL#
#FINALE INVENTORY ENABLE CONNECTION DOWNLOAD#

#FINALE INVENTORY ENABLE CONNECTION DOWNLOAD#

So head over to automation hub or Ansible Galaxy, download the ServiceNow ITSM Ansible Collection, and start exploring. I covered quite a lot yet still only managed to scratch the surface of what is possible.

Who could have thought that one can stuff this much awesomeness into a single playbook? name: Register the newly-created VM instance By default, the _item module will use the cmdb_ci system class name, but you can change it to any other cmdb_ci-derived class. Updating the CMDBīecause the ServiceNow CMDB has more than one configuration item type, you need to specify the sys_class_name parameter when adding new items. However, managing configuration items is a bit different, so let’s focus on this area next. You can interact with problems and change requests in the same manner. You can also delete an existing incident by setting the state parameter to absent. If you run Ansible with the -diff switch, it will report what changes it implemented to the incident record: TASK *************************** Ansible will compare the current and the desired states of the incident and make necessary changes to get them in sync.

#FINALE INVENTORY ENABLE CONNECTION UPDATE#

You can update an existing incident by providing either a ticket number or system id of the incident record. Once the previous playbook finishes executing, you'll find a new incident listed in ServiceNow. The minimal Ansible playbook would look something like this:. Now that you have your credentials ready, you can create a new incident. Do that by setting three environment variables: $ export SN_HOST='' Managing incidents, the Ansible wayĬreating a new incident ticket using Ansible is reasonably straightforward, but before you can do that, you need to tell Ansible where your ServiceNow instance lives and what credentials to use. If Ansible did not yell at us, you're all set. To verify nothing went awry, display the documentation for one of the modules by executing the following command: $ ansible-doc The Certified Content Collection for ServiceNow also contains an inventory plugin called that allows you to use CMDB as an inventory source. _item for managing the CMDBĮach of the modules also has a counterpart that gives you read-only access to ServiceNow records.If everything goes according to plan, you now have access to the following modules:

#FINALE INVENTORY ENABLE CONNECTION INSTALL#

Once you have your credentials, you can install the ServiceNow Collection by running the following command: $ ansible-galaxy collection install sm For details, please refer to the ' Hands On With Ansible Collections' blog post. Before you can access content in the automation hub, you must first configure your credentials in the Ansible configuration file. You can download the sm Collection from automation hub or Ansible Galaxy.

Installing the Certified Content Collection for ServiceNow

Updating the ServiceNow configuration management database (CMDB).

Updating incidents, problems, and change requests.

In this post, I demonstrate a few sample Ansible Playbooks that take care of essential admin tasks such as: ServiceNow modules have an intuitive user interface backed by a robust implementation, offering support for things Ansible users expect (e.g., check mode and change detection). This Collection was designed and developed by the XLAB Steampunk team in close collaboration with Red Hat Ansible, specifically keeping end-users in mind.

Migrating to Ansible Automation Platform 2.

A system administrator's guide to IT automation.

#FINALE INVENTORY ENABLE CONNECTION TRIAL#

Ansible Automation Platform trial subscription.

Finale inventory enable connection