-
Notifications
You must be signed in to change notification settings - Fork 389
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[datadog_security_monitoring_rule] Updating schema validation for field type #1640
Conversation
4c413b1
to
d8eeebc
Compare
3846b12
to
048a207
Compare
048a207
to
19deb61
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 for docs.
Description: "The rule type.", | ||
Default: "log_detection", | ||
Type: schema.TypeString, | ||
ValidateDiagFunc: validators.ValidateStringEnumValue(datadogV2.SECURITYMONITORINGRULETYPEREAD_LOG_DETECTION, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't reuse OOTB validator provided by the TF SDK because:
- documentation is generated by checking the output of the ValidateDiagFunc when passing an
EnumChecker
- PR build fails when manually updating the documentation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'd like to explicitly remove support for
infrastructure_configuration
andcloud_configuration
rules as their management with TF is broken. See RFC for more details.