Skip to content

Commit 67a9dee

Browse files
authored
Merge pull request #386 from hashicorp/repo-sync
Repo sync
2 parents 03faf9c + 31382a1 commit 67a9dee

File tree

2 files changed

+3
-3
lines changed
  • content
    • terraform-docs-common/docs/cloud-docs/users-teams-organizations/teams
    • terraform-enterprise/1.0.x/docs/enterprise/users-teams-organizations/teams

2 files changed

+3
-3
lines changed

content/terraform-docs-common/docs/cloud-docs/users-teams-organizations/teams/notifications.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ description: Learn how to set up team notifications to notify team members on ex
55

66
# Manage team notifications
77

8-
HCP Terraform can use webhooks to notify external systems about run progress, change requests, and other events. Team notifications allow you to configure relevant alerts that notify teams you specify whenever a certain event occurs.
8+
HCP Terraform can use webhooks to notify external systems about events. Team notifications allow you to configure relevant alerts that notify teams you specify whenever a certain event occurs. You can only configure team notifications to notify your team of [change requests](/terraform/cloud-docs/workspaces/change-requests).
99

1010
@include 'tfc-package-callouts/notifications.mdx'
1111

@@ -125,4 +125,4 @@ You can use some of the values in the payload to retrieve additional information
125125

126126
Slack notifications use Slack's own protocols to verify HCP Terraform's webhook requests.
127127

128-
Generic notifications can include a signature to verify the request. For notification configurations that include a secret token, HCP Terraform's webhook requests include an `X-TFE-Notification-Signature` header containing an HMAC signature computed from the token using the SHA-512 digest algorithm. The notification’s receiving service is responsible for validating the signature. For more information and an example of how to validate the signature, refer to the [API documentation](/terraform/cloud-docs/api-docs/notification-configurations#notification-payload).
128+
Generic notifications can include a signature to verify the request. For notification configurations that include a secret token, HCP Terraform's webhook requests include an `X-TFE-Notification-Signature` header containing an HMAC signature computed from the token using the SHA-512 digest algorithm. The notification’s receiving service is responsible for validating the signature. For more information and an example of how to validate the signature, refer to the [API documentation](/terraform/cloud-docs/api-docs/notification-configurations#notification-payload).

content/terraform-enterprise/1.0.x/docs/enterprise/users-teams-organizations/teams/notifications.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ source: terraform-docs-common
88

99
# Manage team notifications
1010

11-
HCP Terraform can use webhooks to notify external systems about run progress, change requests, and other events. Team notifications allow you to configure relevant alerts that notify teams you specify whenever a certain event occurs.
11+
HCP Terraform can use webhooks to notify external systems about events. Team notifications allow you to configure relevant alerts that notify teams you specify whenever a certain event occurs. You can only configure team notifications to notify your team of [change requests](/terraform/enterprise/workspaces/change-requests).
1212

1313
@include 'tfc-package-callouts/notifications.mdx'
1414

0 commit comments

Comments
 (0)