The ServiceNow Service Catalog for Terraform now lets you update existing Terraform workspaces and reprovision resources with new variables.
We are excited to announce the ServiceNow Service Catalog for Terraform has been updated to version 2.3. This latest iteration introduces new items to the Terraform Catalog, providing more robust options for platform teams keen on updating and redeploying their existing Terraform infrastructure — essentially enabling seamless Day 2 operations within the application. Additionally, version 2.3 addresses the issue of duplicate workspace names for customers using multiple ServiceNow instances.
This post covers version 2.3’s new features, including:
Enabling Day 2 operations has long been a highly requested feature in the ServiceNow Service Catalog for Terraform. After setting up their initial workspace and resources, many users wished for easy ways to change details like workspace description or how it runs, or even shift it to a different project within Terraform Cloud or Enterprise. Plus, if a workspace had variables, many users expected a straightforward way to see, change, and then update variable values through the Terraform Catalog.
To address these requests, the latest update introduced new Catalog Items designed to help users set up their own update processes. Whether ServiceNow admins prefer to configure the Catalog Items with Flows or Workflows as a main process engine, there are now specific items they can choose from the Catalog and tweak to meet their specific needs:
When you create a workspace, all its details are now saved in the application’s Terraform database. When you want to update something, the form shows the saved details, making it easy for you to make changes. The values of the variables are also saved. ServiceNow admins now have access to a new Terraform Variables menu module where they can see all these saved variables. These new features work only for workspaces that you set up using the ServiceNow Service Catalog for Terraform.
Version 2.3 of the ServiceNow Service Catalog for Terraform brings an optimized solution for Terraform customers operating with multiple ServiceNow instances connected to a single Terraform Cloud or Enterprise organization.
The app names workspaces based on ServiceNow ticket numbers, and as more workspaces are created within Terraform Cloud or Enterprise, the numbers naturally auto-increment. When multiple instances create new Terraform workspaces at the same time, there is a risk of overlapping numbers.
To mitigate this potential issue, our latest feature enhancement ensures that each Terraform workspace name is unique. Should the app identify a pre-existing workspace with an identical name, it appends a ServiceNow instance ID to the workspace name. This approach maintains consistency and guarantees the distinctive identification of every workspace, ensuring seamless operation across all instances.
The general availability of the latest version of ServiceNow Service Catalog for Terraform Cloud and Terraform Enterprise lets users generate new Terraform workspaces and initiate resource provisioning from the Service Catalog interface. That brings two main benefits:
New catalog items and streamlined multi-instance integrations are available today as generally available features. Learn more by reading thet ServiceNow Service Catalog documentation. And if you haven’t already, get started for free on Terraform Cloud to provision and manage all your infrastructure.
HCP Terraform and Terraform Enterprise enhance permissions management capabilities to eliminate the bottleneck of relying solely on the owner for managing teams.
ServiceNow Service Catalog for Terraform now lets users provision infrastructure powered by no-code modules published in their organization’s private registry.
No-code provisioning module version upgrades are now GA in HCP Terraform, providing validated self-service infrastructure to reduce toil and lower cloud spend.