We’re excited to announce version 2.2 of the ServiceNow Service Catalog integration for HashiCorp Terraform, which helps platform teams and ServiceNow admins standardize and scale their organizations’ cloud adoption by offering self-service provisioning with approved configurations.
Platform teams and admins can securely and efficiently create infrastructure from the ServiceNow Catalog interface based on Terraform code, which is sourced from the version control system attached to their Terraform Cloud organization. The roles and permissions defined in the app empower ServiceNow admins to grant the appropriate level of access to their users and secure data. Downstream users such as app developers and operations teams gain efficiency by using the ServiceNow Catalog request process they're already familiar with without needing to understand how the app is configured at the core.
This post covers version 2.2’s new features, including:
- Execution mode selection for your Terraform workspaces
- Reduction in the number of API calls between your ServiceNow instance and Terraform Cloud
- Enhancements to ServiceNow ticket comments and Terraform configuration testing
Version 2.2 introduces a new feature to the Service Catalog app that allows you to set the execution mode for your Terraform workspaces. There are several modes to choose from:
- The default value is "Remote", which executes in Terraform Cloud’s infrastructure using a consistent, reliable pool of disposable agents.
- Selecting Agent mode allows you to run Terraform operations on isolated, private, or on-premises infrastructure. This option requires you to create an agent pool in your organization beforehand, then provide that agent pool's ID when you order a new workspace through the Service Catalog. Note: Terraform Cloud Agents are available only in the Terraform Cloud Business Tier.
In addition to the new execution mode, the latest version contains performance improvements. Among the most frequently requested updates was reducing API calls between ServiceNow and Terraform Cloud. To achieve this, we introduced additional conditions to the polling mechanism and limited it to shorter intervals. While the exact number may differ depending on the pipeline's size, an average Terraform run with the default on-demand polling setup now incurs only approximately 5 API calls per workspace, compared to the previous 30.
Several enhancements have been made to the ServiceNow RITM ticket comments and configuration testing. With the latest update, you can now monitor all the Terraform run stages and their corresponding timestamps within the ServiceNow ticket interface. Repetitive comments are no longer a concern with the application. Additionally, the previously introduced Test Config button now verifies the connectivity between Terraform Cloud and ServiceNow. This ensures that the Terraform credentials provided to your ServiceNow instance are accurate, allowing you to proceed to the Terraform Catalog orders with confidence.
Getting started with the ServiceNow Service Catalog plugin for Terraform
The Terraform app has been available in the ServiceNow Store for a while and has gained popularity among many users, particularly in organizations that require limited user access and tighter controls over infrastructure security.
Cloud platform teams and ServiceNow admins can get started with the new functionality today using several resources:
- Install the plugin to your ServiceNow instance from the ServiceNow Store
- Set up the Service Catalog integration for Terraform using the documentation available on the HashiCorp Developer website
- Begin working with Terraform Cloud by following our Get Started tutorial or contacting HashiCorp Sales
By combining Terraform Cloud with the ServiceNow Catalog interface, we’re helping cloud platform teams and ServiceNow admins standardize and scale their organization’s cloud adoption with approved configurations that make it easy for developers to focus on building applications and generating revenue for their organizations.
from HashiCorp Blog https://bit.ly/3OhjqjT
Post a Comment