Notification Triggers are now a type string #346
Merged
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.
Description
This PR converts the
Triggers
field in Create/UpdateNotificationConfigurationOpts from[]string
to[]NotificationTriggerType
. I've also added a validation function to ensure any value passed in the array is a validNotificationTriggerType
... the go compiler doesn't enforce it at compile time (See #341).The
Triggers
field forNotificationConfiguration
will remain of type[]string
. This is due to the inability of thejsonapi
package to unmarshal strings into an array of typed strings. Performing some type casting after unmarshalling is an effort that was not deemed to be worthwhile since this is a specific use case.Testing plan
To run integration tests:
go test -run TestNotificationConfiguration -v ./... -tags=integration
Output from tests (HashiCorp employees only)