From 598ac132568311b23ac6e6c67273a9c777dabd0c Mon Sep 17 00:00:00 2001 From: "api-clients-generation-pipeline[bot]" Date: Wed, 21 Aug 2024 18:42:28 +0000 Subject: [PATCH] Add editable field to suppression rule (#2021) Co-authored-by: ci.datadog-api-spec Co-authored-by: api-clients-generation-pipeline[bot] <54105614+api-clients-generation-pipeline[bot]@users.noreply.github.com> a517064667d57ff4572c47e4657ea5324a4c17fd --- datadog_api_client.v2.model.html | 1 + 1 file changed, 1 insertion(+) diff --git a/datadog_api_client.v2.model.html b/datadog_api_client.v2.model.html index 6124caf637..e58a60224a 100644 --- a/datadog_api_client.v2.model.html +++ b/datadog_api_client.v2.model.html @@ -33939,6 +33939,7 @@

SubmodulesSecurityMonitoringUser, optional) – A user.

  • data_exclusion_query (str, optional) – An exclusion query on the input data of the security rules, which could be logs, Agent events, or other types of data based on the security rule. Events matching this query are ignored by any detection rules referenced in the suppression rule.

  • description (str, optional) – A description for the suppression rule.

  • +
  • editable (bool, optional) – Whether the suppression rule is editable.

  • enabled (bool, optional) – Whether the suppression rule is enabled.

  • expiration_date (int, optional) – A Unix millisecond timestamp giving an expiration date for the suppression rule. After this date, it won’t suppress signals anymore.

  • name (str, optional) – The name of the suppression rule.