Feat: add support to webhookSecret in notification API #851
Conversation
This file contains 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
TomerHeber
commented
May 15, 2024
| Name string `json:"name,omitempty"` | ||
| Type NotificationType `json:"type,omitempty"` | ||
| Value string `json:"value,omitempty"` | ||
| WebhookSecret **string `json:"webhookSecret,omitempty" tfschema:"-"` |
There was a problem hiding this comment.
pointer to pointer allows me to support 3 modes:
- passing a string "....". (modify the secret).
- passing a null. (remove the secret)
- omitting the field (no change)
amit-alkobi-env0
approved these changes
May 21, 2024
github-actions
bot
added
ready to merge
| type = "Slack" | ||
| value = "https://someurl1.com" | ||
| name = "${local.notification_name_prefix}-1-${random_string.random.result}" | ||
| type = "Slack" |
There was a problem hiding this comment.
aligned with type body param here
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.
Issue & Steps to Reproduce / Feature Request
resolves #850
Solution