From e35bedd82157413caafec9ac3323d3c6c3a9a978 Mon Sep 17 00:00:00 2001 From: halie-kastl Date: Tue, 3 Jun 2025 08:11:15 -0600 Subject: [PATCH 1/3] Amend token instructions for clarity --- .../service-now/service-catalog-terraform/index.mdx | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx index caa4e1df87..cdd7f297bb 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx @@ -117,10 +117,9 @@ Terraform. 3. On the "ServiceNow" team's settings page, generate a [team API token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). **Save the team API token for later.** -4. After [generating a team token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens) in HCP Terraform, you can add that token to your ServiceNow context by doing the following: - 1. Navigate to **Terraform Configs** in ServiceNow - 2. Select **New** and add your token. - 3. Use your HCP Terraform team name as your **Org name**. +4. After [generating a team token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens) in HCP Terraform, you can add that token to ServiceNow by doing the following: + 1. Navigate to **All > Terraform > Configs** in ServiceNow + 2. Select **New** and add your token and Org Name. 5. If you are using the [VCS flow](/terraform/cloud-docs/integrations/service-now/service-catalog-terraform/service-catalog-config#vcs-configuration): 1. Ensure your Terraform organization is [connected to a VCS provider](/terraform/cloud-docs/vcs). Repositories that are connectable to HCP Terraform workspaces can also be used as workspace templates in the ServiceNow integration. 2. On your organization's VCS provider settings page (**Settings** > **VCS Providers**), find the OAuth Token ID for the VCS provider(s) that you intend to use with the ServiceNow integration. HCP Terraform uses the OAuth token ID to identify and authorize the VCS provider. **Save the OAuth token ID for later.** From 4a5d363f90ab488b774f31f98a5ba4e33e4dec7c Mon Sep 17 00:00:00 2001 From: halie-kastl Date: Tue, 3 Jun 2025 10:44:14 -0600 Subject: [PATCH 2/3] consolidate info, remove repeat --- .../service-now/service-catalog-terraform/index.mdx | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx index cdd7f297bb..93f0a34221 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx @@ -110,16 +110,12 @@ Terraform. **Save the organization name for later.** 2. [Create a team](/terraform/cloud-docs/users-teams-organizations/teams) for that organization called "ServiceNow", and ensure that it has [permission to - manage - workspaces](/terraform/cloud-docs/users-teams-organizations/permissions#manage-all-workspaces). + manage workspaces](/terraform/cloud-docs/users-teams-organizations/permissions#manage-all-workspaces). You do not need to add any users to this team. [permissions-citation]: #intentionally-unused---keep-for-maintainers 3. On the "ServiceNow" team's settings page, generate a [team API - token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). + token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). HCP Terraform now supports fine-grained permissions for team tokens at the project level. You can assign teams and their associated tokens permission levels on specific projects. To learn more about the different permissions necessary to provision resources, refer to [Permissions](/terraform/cloud-docs/users-teams-organizations/permissions#project-permissions). **Save the team API token for later.** -4. After [generating a team token](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens) in HCP Terraform, you can add that token to ServiceNow by doing the following: - 1. Navigate to **All > Terraform > Configs** in ServiceNow - 2. Select **New** and add your token and Org Name. 5. If you are using the [VCS flow](/terraform/cloud-docs/integrations/service-now/service-catalog-terraform/service-catalog-config#vcs-configuration): 1. Ensure your Terraform organization is [connected to a VCS provider](/terraform/cloud-docs/vcs). Repositories that are connectable to HCP Terraform workspaces can also be used as workspace templates in the ServiceNow integration. 2. On your organization's VCS provider settings page (**Settings** > **VCS Providers**), find the OAuth Token ID for the VCS provider(s) that you intend to use with the ServiceNow integration. HCP Terraform uses the OAuth token ID to identify and authorize the VCS provider. **Save the OAuth token ID for later.** @@ -223,8 +219,7 @@ update request items. ### Team Tokens Team-scoped tokens can help you manage a team's access to things in HCP Terraform, but team tokens are limited within the ServiceNow context. We recommend only using one API team token, regardless of the number of teams accessing ServiceNow. - -You can assign teams and their associated tokens permission levels on specific projects. To learn more about the different permissions necessary to provision resources, refer to [Permissions](/terraform/cloud-docs/users-teams-organizations/permissions#project-permissions). To learn more about API tokens, refer to [Team tokens](https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). +To learn more about API tokens, refer to [Team tokens](https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). ### ServiceNow Developer Reference From 962fb4358e0bffafdf755b3b2f396557d051b151 Mon Sep 17 00:00:00 2001 From: Rose M Koron <32436232+rkoron007@users.noreply.github.com> Date: Thu, 5 Jun 2025 12:13:09 -0700 Subject: [PATCH 3/3] Apply suggestions from code review --- .../service-now/service-catalog-terraform/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx b/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx index 93f0a34221..e1229f4188 100644 --- a/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx +++ b/content/terraform-docs-common/docs/cloud-docs/integrations/service-now/service-catalog-terraform/index.mdx @@ -219,7 +219,7 @@ update request items. ### Team Tokens Team-scoped tokens can help you manage a team's access to things in HCP Terraform, but team tokens are limited within the ServiceNow context. We recommend only using one API team token, regardless of the number of teams accessing ServiceNow. -To learn more about API tokens, refer to [Team tokens](https://developer.hashicorp.com/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). +To learn more about API tokens, refer to [Team tokens](/terraform/cloud-docs/users-teams-organizations/api-tokens#team-api-tokens). ### ServiceNow Developer Reference