[TF-28096] Clarify events that team notifications can subscribe to #866
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Team notifications can only subscribe to change requests, and have never had run progress or other events available as options for subscription. Clarifying the docs here to avoid confusion in the future
|
|
|
Thank you for your submission! We require that all contributors sign our Contributor License Agreement ("CLA") before we can accept the contribution. Read and sign the agreement Learn more about why HashiCorp requires a CLA and what the CLA includes Have you signed the CLA already but the status is still pending? Recheck it. |
Vercel Previews Deployed
|
nylkotuby
commented
Aug 26, 2025
| 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). |
There was a problem hiding this comment.
No actual diff on this line, CRLF
nylkotuby
commented
Aug 26, 2025
There was a problem hiding this comment.
Wasn't sure how to address enterprise in this change, lmk if this is appropriate
Broken Link CheckerNo broken links found! 🎉 |
rkoron007
approved these changes
Sep 4, 2025
content/terraform-docs-common/docs/cloud-docs/users-teams-organizations/teams/notifications.mdx
Outdated
Show resolved
Hide resolved
...terraform-enterprise/1.0.x/docs/enterprise/users-teams-organizations/teams/notifications.mdx
Outdated
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Team notifications can only subscribe to change requests, and have never had run progress or other events available as options for subscription. Clarifying the docs here to avoid confusion in the future, the team will update the docs when this feature supports other event types in the future.
JIRA