From 92c8b5c59eba61441d96409710ea7163e87dede8 Mon Sep 17 00:00:00 2001 From: Ofek Lev Date: Mon, 28 Feb 2022 23:24:27 -0500 Subject: [PATCH] Remove outdated warning in the description for the `tls_ignore_warning` option --- .../datadog_checks/activemq_xml/data/conf.yaml.example | 4 ---- airflow/datadog_checks/airflow/data/conf.yaml.example | 4 ---- amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example | 4 ---- ambari/datadog_checks/ambari/data/conf.yaml.example | 4 ---- apache/datadog_checks/apache/data/conf.yaml.example | 4 ---- .../datadog_checks/avi_vantage/data/conf.yaml.example | 4 ---- .../datadog_checks/azure_iot_edge/data/conf.yaml.example | 4 ---- cilium/datadog_checks/cilium/data/conf.yaml.example | 4 ---- cisco_aci/datadog_checks/cisco_aci/data/conf.yaml.example | 4 ---- .../datadog_checks/citrix_hypervisor/data/conf.yaml.example | 4 ---- .../datadog_checks/cloud_foundry_api/data/conf.yaml.example | 4 ---- .../datadog_checks/cockroachdb/data/conf.yaml.example | 4 ---- consul/datadog_checks/consul/data/conf.yaml.example | 4 ---- coredns/datadog_checks/coredns/data/conf.yaml.example | 4 ---- couch/datadog_checks/couch/data/conf.yaml.example | 4 ---- couchbase/datadog_checks/couchbase/data/conf.yaml.example | 4 ---- crio/datadog_checks/crio/data/conf.yaml.example | 4 ---- .../dev/tooling/templates/configuration/instances/http.yaml | 6 +----- .../datadog_cluster_agent/data/auto_conf.yaml | 4 ---- .../datadog_cluster_agent/data/conf.yaml.example | 4 ---- druid/datadog_checks/druid/data/conf.yaml.example | 4 ---- .../datadog_checks/ecs_fargate/data/conf.yaml.example | 4 ---- .../datadog_checks/eks_fargate/data/conf.yaml.example | 4 ---- elastic/datadog_checks/elastic/data/conf.yaml.example | 4 ---- envoy/datadog_checks/envoy/data/conf.yaml.example | 4 ---- etcd/datadog_checks/etcd/data/conf.yaml.example | 4 ---- .../datadog_checks/external_dns/data/conf.yaml.example | 4 ---- fluentd/datadog_checks/fluentd/data/conf.yaml.example | 4 ---- gitlab/datadog_checks/gitlab/data/conf.yaml.example | 4 ---- .../datadog_checks/gitlab_runner/data/conf.yaml.example | 4 ---- go_expvar/datadog_checks/go_expvar/data/conf.yaml.example | 4 ---- haproxy/datadog_checks/haproxy/data/conf.yaml.example | 4 ---- harbor/datadog_checks/harbor/data/conf.yaml.example | 4 ---- hazelcast/datadog_checks/hazelcast/data/conf.yaml.example | 4 ---- .../datadog_checks/hdfs_datanode/data/conf.yaml.example | 4 ---- .../datadog_checks/hdfs_namenode/data/conf.yaml.example | 4 ---- http_check/datadog_checks/http_check/data/conf.yaml.example | 4 ---- ibm_was/datadog_checks/ibm_was/data/conf.yaml.example | 4 ---- istio/datadog_checks/istio/data/conf.yaml.example | 4 ---- kong/datadog_checks/kong/data/conf.yaml.example | 4 ---- .../kube_apiserver_metrics/data/conf.yaml.example | 4 ---- .../kube_controller_manager/data/conf.yaml.example | 4 ---- kube_dns/datadog_checks/kube_dns/data/conf.yaml.example | 4 ---- .../kube_metrics_server/data/conf.yaml.example | 4 ---- kube_proxy/datadog_checks/kube_proxy/data/conf.yaml.example | 4 ---- .../datadog_checks/kube_scheduler/data/conf.yaml.example | 4 ---- kubelet/datadog_checks/kubelet/data/conf.yaml.example | 4 ---- .../datadog_checks/kubernetes_state/data/conf.yaml.example | 4 ---- .../datadog_checks/kyototycoon/data/conf.yaml.example | 4 ---- lighttpd/datadog_checks/lighttpd/data/conf.yaml.example | 4 ---- linkerd/datadog_checks/linkerd/data/conf.yaml.example | 4 ---- mapreduce/datadog_checks/mapreduce/data/conf.yaml.example | 4 ---- marathon/datadog_checks/marathon/data/conf.yaml.example | 4 ---- marklogic/datadog_checks/marklogic/data/conf.yaml.example | 4 ---- .../datadog_checks/mesos_master/data/conf.yaml.example | 4 ---- .../datadog_checks/mesos_slave/data/conf.yaml.example | 4 ---- nginx/datadog_checks/nginx/data/conf.yaml.example | 4 ---- .../nginx_ingress_controller/data/conf.yaml.example | 4 ---- .../datadog_checks/openmetrics/data/conf.yaml.example | 4 ---- .../openstack_controller/data/conf.yaml.example | 4 ---- php_fpm/datadog_checks/php_fpm/data/conf.yaml.example | 4 ---- .../datadog_checks/powerdns_recursor/data/conf.yaml.example | 4 ---- pulsar/datadog_checks/pulsar/data/conf.yaml.example | 4 ---- rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example | 4 ---- riak/datadog_checks/riak/data/conf.yaml.example | 4 ---- scylla/datadog_checks/scylla/data/conf.yaml.example | 4 ---- silk/datadog_checks/silk/data/conf.yaml.example | 4 ---- sonarqube/datadog_checks/sonarqube/data/conf.yaml.example | 4 ---- spark/datadog_checks/spark/data/conf.yaml.example | 4 ---- squid/datadog_checks/squid/data/conf.yaml.example | 4 ---- teamcity/datadog_checks/teamcity/data/conf.yaml.example | 4 ---- twistlock/datadog_checks/twistlock/data/conf.yaml.example | 4 ---- vault/datadog_checks/vault/data/conf.yaml.example | 4 ---- voltdb/datadog_checks/voltdb/data/conf.yaml.example | 4 ---- vsphere/datadog_checks/vsphere/data/conf.yaml.example | 4 ---- yarn/datadog_checks/yarn/data/conf.yaml.example | 4 ---- 76 files changed, 1 insertion(+), 305 deletions(-) diff --git a/activemq_xml/datadog_checks/activemq_xml/data/conf.yaml.example b/activemq_xml/datadog_checks/activemq_xml/data/conf.yaml.example index a9a6aa528bbfa..a0b73b4ac63c9 100644 --- a/activemq_xml/datadog_checks/activemq_xml/data/conf.yaml.example +++ b/activemq_xml/datadog_checks/activemq_xml/data/conf.yaml.example @@ -286,10 +286,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/airflow/datadog_checks/airflow/data/conf.yaml.example b/airflow/datadog_checks/airflow/data/conf.yaml.example index 71191fa6846c6..e5970bfa28a17 100644 --- a/airflow/datadog_checks/airflow/data/conf.yaml.example +++ b/airflow/datadog_checks/airflow/data/conf.yaml.example @@ -257,10 +257,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example b/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example index 93908fe91e1a0..372feabd81b1b 100644 --- a/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example +++ b/amazon_msk/datadog_checks/amazon_msk/data/conf.yaml.example @@ -525,10 +525,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/ambari/datadog_checks/ambari/data/conf.yaml.example b/ambari/datadog_checks/ambari/data/conf.yaml.example index 9f8d7edb5a921..a2312b3808fe9 100644 --- a/ambari/datadog_checks/ambari/data/conf.yaml.example +++ b/ambari/datadog_checks/ambari/data/conf.yaml.example @@ -286,10 +286,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/apache/datadog_checks/apache/data/conf.yaml.example b/apache/datadog_checks/apache/data/conf.yaml.example index d5a47108f792a..6935e52c3b4e0 100644 --- a/apache/datadog_checks/apache/data/conf.yaml.example +++ b/apache/datadog_checks/apache/data/conf.yaml.example @@ -257,10 +257,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example b/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example index d25590ccecdcd..2dbae8a8512cb 100644 --- a/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example +++ b/avi_vantage/datadog_checks/avi_vantage/data/conf.yaml.example @@ -485,10 +485,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/azure_iot_edge/datadog_checks/azure_iot_edge/data/conf.yaml.example b/azure_iot_edge/datadog_checks/azure_iot_edge/data/conf.yaml.example index 066e994a1b023..44ced4c09b07c 100644 --- a/azure_iot_edge/datadog_checks/azure_iot_edge/data/conf.yaml.example +++ b/azure_iot_edge/datadog_checks/azure_iot_edge/data/conf.yaml.example @@ -392,10 +392,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/cilium/datadog_checks/cilium/data/conf.yaml.example b/cilium/datadog_checks/cilium/data/conf.yaml.example index 84d3807c664c7..cc836bf66baa9 100644 --- a/cilium/datadog_checks/cilium/data/conf.yaml.example +++ b/cilium/datadog_checks/cilium/data/conf.yaml.example @@ -490,10 +490,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/cisco_aci/datadog_checks/cisco_aci/data/conf.yaml.example b/cisco_aci/datadog_checks/cisco_aci/data/conf.yaml.example index 1028cc5c4ce92..29fb49ffc6ea9 100644 --- a/cisco_aci/datadog_checks/cisco_aci/data/conf.yaml.example +++ b/cisco_aci/datadog_checks/cisco_aci/data/conf.yaml.example @@ -201,10 +201,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/citrix_hypervisor/datadog_checks/citrix_hypervisor/data/conf.yaml.example b/citrix_hypervisor/datadog_checks/citrix_hypervisor/data/conf.yaml.example index 4c61561484a52..06b03800efc4b 100644 --- a/citrix_hypervisor/datadog_checks/citrix_hypervisor/data/conf.yaml.example +++ b/citrix_hypervisor/datadog_checks/citrix_hypervisor/data/conf.yaml.example @@ -257,10 +257,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/cloud_foundry_api/datadog_checks/cloud_foundry_api/data/conf.yaml.example b/cloud_foundry_api/datadog_checks/cloud_foundry_api/data/conf.yaml.example index 39d18cee377d3..15021f52e359a 100644 --- a/cloud_foundry_api/datadog_checks/cloud_foundry_api/data/conf.yaml.example +++ b/cloud_foundry_api/datadog_checks/cloud_foundry_api/data/conf.yaml.example @@ -140,10 +140,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example b/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example index 8166447a4d121..0f260f27be2da 100644 --- a/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example +++ b/cockroachdb/datadog_checks/cockroachdb/data/conf.yaml.example @@ -475,10 +475,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/consul/datadog_checks/consul/data/conf.yaml.example b/consul/datadog_checks/consul/data/conf.yaml.example index 8214ea2e93f7c..a9010c6e1dcba 100644 --- a/consul/datadog_checks/consul/data/conf.yaml.example +++ b/consul/datadog_checks/consul/data/conf.yaml.example @@ -340,10 +340,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/coredns/datadog_checks/coredns/data/conf.yaml.example b/coredns/datadog_checks/coredns/data/conf.yaml.example index b95b34d97aec5..20da92cea7f65 100644 --- a/coredns/datadog_checks/coredns/data/conf.yaml.example +++ b/coredns/datadog_checks/coredns/data/conf.yaml.example @@ -500,10 +500,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/couch/datadog_checks/couch/data/conf.yaml.example b/couch/datadog_checks/couch/data/conf.yaml.example index d1bce8dbe197d..d64f791b4a7b6 100644 --- a/couch/datadog_checks/couch/data/conf.yaml.example +++ b/couch/datadog_checks/couch/data/conf.yaml.example @@ -322,10 +322,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/couchbase/datadog_checks/couchbase/data/conf.yaml.example b/couchbase/datadog_checks/couchbase/data/conf.yaml.example index 7ab80c602dbee..ff032883e12df 100644 --- a/couchbase/datadog_checks/couchbase/data/conf.yaml.example +++ b/couchbase/datadog_checks/couchbase/data/conf.yaml.example @@ -275,10 +275,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/crio/datadog_checks/crio/data/conf.yaml.example b/crio/datadog_checks/crio/data/conf.yaml.example index acc9d683dfa43..cbb8827cf32ec 100644 --- a/crio/datadog_checks/crio/data/conf.yaml.example +++ b/crio/datadog_checks/crio/data/conf.yaml.example @@ -387,10 +387,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/http.yaml b/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/http.yaml index 1a9ee69aa219f..4d8865d9e21fd 100644 --- a/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/http.yaml +++ b/datadog_checks_dev/datadog_checks/dev/tooling/templates/configuration/instances/http.yaml @@ -235,10 +235,6 @@ description: | If `tls_verify` is disabled, security warnings are logged by the check. Disable those by setting `tls_ignore_warning` to true. - - Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - to true. - name: tls_cert value: example: @@ -335,4 +331,4 @@ value: example: true type: boolean - description: Whether or not to allow URL redirection. + description: Whether or not to allow URL redirection. diff --git a/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/auto_conf.yaml b/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/auto_conf.yaml index fdbb456c74599..f79758e23c820 100644 --- a/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/auto_conf.yaml +++ b/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/auto_conf.yaml @@ -395,10 +395,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/conf.yaml.example b/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/conf.yaml.example index b0d7758f202aa..356a4b00e10da 100644 --- a/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/conf.yaml.example +++ b/datadog_cluster_agent/datadog_checks/datadog_cluster_agent/data/conf.yaml.example @@ -387,10 +387,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/druid/datadog_checks/druid/data/conf.yaml.example b/druid/datadog_checks/druid/data/conf.yaml.example index dc1607dd2a9f5..0ecefe85d4055 100644 --- a/druid/datadog_checks/druid/data/conf.yaml.example +++ b/druid/datadog_checks/druid/data/conf.yaml.example @@ -257,10 +257,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/ecs_fargate/datadog_checks/ecs_fargate/data/conf.yaml.example b/ecs_fargate/datadog_checks/ecs_fargate/data/conf.yaml.example index 86202787936f3..81154f6c54e92 100644 --- a/ecs_fargate/datadog_checks/ecs_fargate/data/conf.yaml.example +++ b/ecs_fargate/datadog_checks/ecs_fargate/data/conf.yaml.example @@ -253,10 +253,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/eks_fargate/datadog_checks/eks_fargate/data/conf.yaml.example b/eks_fargate/datadog_checks/eks_fargate/data/conf.yaml.example index 89aa9a6a498e3..dd8cf03cf57b1 100644 --- a/eks_fargate/datadog_checks/eks_fargate/data/conf.yaml.example +++ b/eks_fargate/datadog_checks/eks_fargate/data/conf.yaml.example @@ -253,10 +253,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/elastic/datadog_checks/elastic/data/conf.yaml.example b/elastic/datadog_checks/elastic/data/conf.yaml.example index 15889e9157306..790b6c078a967 100644 --- a/elastic/datadog_checks/elastic/data/conf.yaml.example +++ b/elastic/datadog_checks/elastic/data/conf.yaml.example @@ -418,10 +418,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/envoy/datadog_checks/envoy/data/conf.yaml.example b/envoy/datadog_checks/envoy/data/conf.yaml.example index 3a4d1cbb971aa..c219bba6e902d 100644 --- a/envoy/datadog_checks/envoy/data/conf.yaml.example +++ b/envoy/datadog_checks/envoy/data/conf.yaml.example @@ -486,10 +486,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/etcd/datadog_checks/etcd/data/conf.yaml.example b/etcd/datadog_checks/etcd/data/conf.yaml.example index 2d423c6c12e6b..ae3ed602b8920 100644 --- a/etcd/datadog_checks/etcd/data/conf.yaml.example +++ b/etcd/datadog_checks/etcd/data/conf.yaml.example @@ -393,10 +393,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/external_dns/datadog_checks/external_dns/data/conf.yaml.example b/external_dns/datadog_checks/external_dns/data/conf.yaml.example index d34ecaea16610..4bea1aa4d8e5d 100644 --- a/external_dns/datadog_checks/external_dns/data/conf.yaml.example +++ b/external_dns/datadog_checks/external_dns/data/conf.yaml.example @@ -387,10 +387,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/fluentd/datadog_checks/fluentd/data/conf.yaml.example b/fluentd/datadog_checks/fluentd/data/conf.yaml.example index c1b3a4b947843..b02bc7ccbb4de 100644 --- a/fluentd/datadog_checks/fluentd/data/conf.yaml.example +++ b/fluentd/datadog_checks/fluentd/data/conf.yaml.example @@ -310,10 +310,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/gitlab/datadog_checks/gitlab/data/conf.yaml.example b/gitlab/datadog_checks/gitlab/data/conf.yaml.example index 26e8b12d10a89..8e001d63ff737 100644 --- a/gitlab/datadog_checks/gitlab/data/conf.yaml.example +++ b/gitlab/datadog_checks/gitlab/data/conf.yaml.example @@ -358,10 +358,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/gitlab_runner/datadog_checks/gitlab_runner/data/conf.yaml.example b/gitlab_runner/datadog_checks/gitlab_runner/data/conf.yaml.example index 8fe34267e2411..21701fa119930 100644 --- a/gitlab_runner/datadog_checks/gitlab_runner/data/conf.yaml.example +++ b/gitlab_runner/datadog_checks/gitlab_runner/data/conf.yaml.example @@ -441,10 +441,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/go_expvar/datadog_checks/go_expvar/data/conf.yaml.example b/go_expvar/datadog_checks/go_expvar/data/conf.yaml.example index cdb7785d43f24..93d453becc715 100644 --- a/go_expvar/datadog_checks/go_expvar/data/conf.yaml.example +++ b/go_expvar/datadog_checks/go_expvar/data/conf.yaml.example @@ -296,10 +296,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/haproxy/datadog_checks/haproxy/data/conf.yaml.example b/haproxy/datadog_checks/haproxy/data/conf.yaml.example index 1fdf829333d90..e9b9f32f46e65 100644 --- a/haproxy/datadog_checks/haproxy/data/conf.yaml.example +++ b/haproxy/datadog_checks/haproxy/data/conf.yaml.example @@ -486,10 +486,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/harbor/datadog_checks/harbor/data/conf.yaml.example b/harbor/datadog_checks/harbor/data/conf.yaml.example index 0a38d3bdf6e82..51af2e31d5a3f 100644 --- a/harbor/datadog_checks/harbor/data/conf.yaml.example +++ b/harbor/datadog_checks/harbor/data/conf.yaml.example @@ -259,10 +259,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/hazelcast/datadog_checks/hazelcast/data/conf.yaml.example b/hazelcast/datadog_checks/hazelcast/data/conf.yaml.example index 092cb8f533d31..f4f32b4891936 100644 --- a/hazelcast/datadog_checks/hazelcast/data/conf.yaml.example +++ b/hazelcast/datadog_checks/hazelcast/data/conf.yaml.example @@ -434,10 +434,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/hdfs_datanode/datadog_checks/hdfs_datanode/data/conf.yaml.example b/hdfs_datanode/datadog_checks/hdfs_datanode/data/conf.yaml.example index 93488a5d8b846..2f80c07d8784f 100644 --- a/hdfs_datanode/datadog_checks/hdfs_datanode/data/conf.yaml.example +++ b/hdfs_datanode/datadog_checks/hdfs_datanode/data/conf.yaml.example @@ -263,10 +263,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/hdfs_namenode/datadog_checks/hdfs_namenode/data/conf.yaml.example b/hdfs_namenode/datadog_checks/hdfs_namenode/data/conf.yaml.example index c5ec37c4b9fc8..a9e0600746f9e 100644 --- a/hdfs_namenode/datadog_checks/hdfs_namenode/data/conf.yaml.example +++ b/hdfs_namenode/datadog_checks/hdfs_namenode/data/conf.yaml.example @@ -263,10 +263,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/http_check/datadog_checks/http_check/data/conf.yaml.example b/http_check/datadog_checks/http_check/data/conf.yaml.example index f3ea4b3665fd6..29c692b82ab54 100644 --- a/http_check/datadog_checks/http_check/data/conf.yaml.example +++ b/http_check/datadog_checks/http_check/data/conf.yaml.example @@ -418,10 +418,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/ibm_was/datadog_checks/ibm_was/data/conf.yaml.example b/ibm_was/datadog_checks/ibm_was/data/conf.yaml.example index 76845026acfbc..46ba92795fcca 100644 --- a/ibm_was/datadog_checks/ibm_was/data/conf.yaml.example +++ b/ibm_was/datadog_checks/ibm_was/data/conf.yaml.example @@ -258,10 +258,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/istio/datadog_checks/istio/data/conf.yaml.example b/istio/datadog_checks/istio/data/conf.yaml.example index 2ed6b39a620fd..b038c9710c77b 100644 --- a/istio/datadog_checks/istio/data/conf.yaml.example +++ b/istio/datadog_checks/istio/data/conf.yaml.example @@ -492,10 +492,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kong/datadog_checks/kong/data/conf.yaml.example b/kong/datadog_checks/kong/data/conf.yaml.example index 6c6f05ab0c9c6..b2ab5aa4fbf0d 100644 --- a/kong/datadog_checks/kong/data/conf.yaml.example +++ b/kong/datadog_checks/kong/data/conf.yaml.example @@ -485,10 +485,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kube_apiserver_metrics/datadog_checks/kube_apiserver_metrics/data/conf.yaml.example b/kube_apiserver_metrics/datadog_checks/kube_apiserver_metrics/data/conf.yaml.example index 51b62b4e48c00..1ee2e400a174a 100644 --- a/kube_apiserver_metrics/datadog_checks/kube_apiserver_metrics/data/conf.yaml.example +++ b/kube_apiserver_metrics/datadog_checks/kube_apiserver_metrics/data/conf.yaml.example @@ -394,10 +394,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kube_controller_manager/datadog_checks/kube_controller_manager/data/conf.yaml.example b/kube_controller_manager/datadog_checks/kube_controller_manager/data/conf.yaml.example index ce675bb3ec35c..380ed5c42a133 100644 --- a/kube_controller_manager/datadog_checks/kube_controller_manager/data/conf.yaml.example +++ b/kube_controller_manager/datadog_checks/kube_controller_manager/data/conf.yaml.example @@ -429,10 +429,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kube_dns/datadog_checks/kube_dns/data/conf.yaml.example b/kube_dns/datadog_checks/kube_dns/data/conf.yaml.example index 17ec8f8f163c4..fee2f903a0932 100644 --- a/kube_dns/datadog_checks/kube_dns/data/conf.yaml.example +++ b/kube_dns/datadog_checks/kube_dns/data/conf.yaml.example @@ -387,10 +387,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kube_metrics_server/datadog_checks/kube_metrics_server/data/conf.yaml.example b/kube_metrics_server/datadog_checks/kube_metrics_server/data/conf.yaml.example index 8fbbdf3fcaeed..a650a154538b4 100644 --- a/kube_metrics_server/datadog_checks/kube_metrics_server/data/conf.yaml.example +++ b/kube_metrics_server/datadog_checks/kube_metrics_server/data/conf.yaml.example @@ -394,10 +394,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kube_proxy/datadog_checks/kube_proxy/data/conf.yaml.example b/kube_proxy/datadog_checks/kube_proxy/data/conf.yaml.example index 68931f0cccfe7..66ba1c2ec63f3 100644 --- a/kube_proxy/datadog_checks/kube_proxy/data/conf.yaml.example +++ b/kube_proxy/datadog_checks/kube_proxy/data/conf.yaml.example @@ -387,10 +387,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kube_scheduler/datadog_checks/kube_scheduler/data/conf.yaml.example b/kube_scheduler/datadog_checks/kube_scheduler/data/conf.yaml.example index dfd82591f9e75..80c051b65727f 100644 --- a/kube_scheduler/datadog_checks/kube_scheduler/data/conf.yaml.example +++ b/kube_scheduler/datadog_checks/kube_scheduler/data/conf.yaml.example @@ -408,10 +408,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kubelet/datadog_checks/kubelet/data/conf.yaml.example b/kubelet/datadog_checks/kubelet/data/conf.yaml.example index 1d0b3f15e749d..85673877709c3 100644 --- a/kubelet/datadog_checks/kubelet/data/conf.yaml.example +++ b/kubelet/datadog_checks/kubelet/data/conf.yaml.example @@ -410,10 +410,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kubernetes_state/datadog_checks/kubernetes_state/data/conf.yaml.example b/kubernetes_state/datadog_checks/kubernetes_state/data/conf.yaml.example index e8ce5d77d3afe..36808f8244988 100644 --- a/kubernetes_state/datadog_checks/kubernetes_state/data/conf.yaml.example +++ b/kubernetes_state/datadog_checks/kubernetes_state/data/conf.yaml.example @@ -382,10 +382,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/kyototycoon/datadog_checks/kyototycoon/data/conf.yaml.example b/kyototycoon/datadog_checks/kyototycoon/data/conf.yaml.example index 10b0732261d9c..8485a658438d4 100644 --- a/kyototycoon/datadog_checks/kyototycoon/data/conf.yaml.example +++ b/kyototycoon/datadog_checks/kyototycoon/data/conf.yaml.example @@ -262,10 +262,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/lighttpd/datadog_checks/lighttpd/data/conf.yaml.example b/lighttpd/datadog_checks/lighttpd/data/conf.yaml.example index e2e310f9b092d..5684eceeaa1e5 100644 --- a/lighttpd/datadog_checks/lighttpd/data/conf.yaml.example +++ b/lighttpd/datadog_checks/lighttpd/data/conf.yaml.example @@ -257,10 +257,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/linkerd/datadog_checks/linkerd/data/conf.yaml.example b/linkerd/datadog_checks/linkerd/data/conf.yaml.example index 94dcfdbbafd01..a229cd1e8a55c 100644 --- a/linkerd/datadog_checks/linkerd/data/conf.yaml.example +++ b/linkerd/datadog_checks/linkerd/data/conf.yaml.example @@ -475,10 +475,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/mapreduce/datadog_checks/mapreduce/data/conf.yaml.example b/mapreduce/datadog_checks/mapreduce/data/conf.yaml.example index 042db147f1ba0..451889c4252ae 100644 --- a/mapreduce/datadog_checks/mapreduce/data/conf.yaml.example +++ b/mapreduce/datadog_checks/mapreduce/data/conf.yaml.example @@ -319,10 +319,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/marathon/datadog_checks/marathon/data/conf.yaml.example b/marathon/datadog_checks/marathon/data/conf.yaml.example index d1b1bb38303df..317c6cb914fc7 100644 --- a/marathon/datadog_checks/marathon/data/conf.yaml.example +++ b/marathon/datadog_checks/marathon/data/conf.yaml.example @@ -308,10 +308,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/marklogic/datadog_checks/marklogic/data/conf.yaml.example b/marklogic/datadog_checks/marklogic/data/conf.yaml.example index e3828e4be364f..c874145778748 100644 --- a/marklogic/datadog_checks/marklogic/data/conf.yaml.example +++ b/marklogic/datadog_checks/marklogic/data/conf.yaml.example @@ -281,10 +281,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/mesos_master/datadog_checks/mesos_master/data/conf.yaml.example b/mesos_master/datadog_checks/mesos_master/data/conf.yaml.example index 7d309dc6cbca6..4569ff0e8520f 100644 --- a/mesos_master/datadog_checks/mesos_master/data/conf.yaml.example +++ b/mesos_master/datadog_checks/mesos_master/data/conf.yaml.example @@ -263,10 +263,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/mesos_slave/datadog_checks/mesos_slave/data/conf.yaml.example b/mesos_slave/datadog_checks/mesos_slave/data/conf.yaml.example index ff5cdc87b329b..c323372f9da24 100644 --- a/mesos_slave/datadog_checks/mesos_slave/data/conf.yaml.example +++ b/mesos_slave/datadog_checks/mesos_slave/data/conf.yaml.example @@ -280,10 +280,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/nginx/datadog_checks/nginx/data/conf.yaml.example b/nginx/datadog_checks/nginx/data/conf.yaml.example index 313f0a3972396..114bdb6ba0468 100644 --- a/nginx/datadog_checks/nginx/data/conf.yaml.example +++ b/nginx/datadog_checks/nginx/data/conf.yaml.example @@ -301,10 +301,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/nginx_ingress_controller/datadog_checks/nginx_ingress_controller/data/conf.yaml.example b/nginx_ingress_controller/datadog_checks/nginx_ingress_controller/data/conf.yaml.example index fa6227a603931..9b802ac754af4 100644 --- a/nginx_ingress_controller/datadog_checks/nginx_ingress_controller/data/conf.yaml.example +++ b/nginx_ingress_controller/datadog_checks/nginx_ingress_controller/data/conf.yaml.example @@ -395,10 +395,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example b/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example index fa3937199a787..3b7e8aec3b438 100644 --- a/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example +++ b/openmetrics/datadog_checks/openmetrics/data/conf.yaml.example @@ -521,10 +521,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/openstack_controller/datadog_checks/openstack_controller/data/conf.yaml.example b/openstack_controller/datadog_checks/openstack_controller/data/conf.yaml.example index dd5a96c7bdc0b..9a0630e0aa4bc 100644 --- a/openstack_controller/datadog_checks/openstack_controller/data/conf.yaml.example +++ b/openstack_controller/datadog_checks/openstack_controller/data/conf.yaml.example @@ -277,10 +277,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/php_fpm/datadog_checks/php_fpm/data/conf.yaml.example b/php_fpm/datadog_checks/php_fpm/data/conf.yaml.example index d0ac80e2b4919..774595534b5f7 100644 --- a/php_fpm/datadog_checks/php_fpm/data/conf.yaml.example +++ b/php_fpm/datadog_checks/php_fpm/data/conf.yaml.example @@ -293,10 +293,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/powerdns_recursor/datadog_checks/powerdns_recursor/data/conf.yaml.example b/powerdns_recursor/datadog_checks/powerdns_recursor/data/conf.yaml.example index 37ce3e7790035..f1ed23c17267a 100644 --- a/powerdns_recursor/datadog_checks/powerdns_recursor/data/conf.yaml.example +++ b/powerdns_recursor/datadog_checks/powerdns_recursor/data/conf.yaml.example @@ -282,10 +282,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/pulsar/datadog_checks/pulsar/data/conf.yaml.example b/pulsar/datadog_checks/pulsar/data/conf.yaml.example index f35517144af80..09de1e225da18 100644 --- a/pulsar/datadog_checks/pulsar/data/conf.yaml.example +++ b/pulsar/datadog_checks/pulsar/data/conf.yaml.example @@ -474,10 +474,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example b/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example index afc117fb4e713..4e67c3242629a 100644 --- a/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example +++ b/rabbitmq/datadog_checks/rabbitmq/data/conf.yaml.example @@ -349,10 +349,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/riak/datadog_checks/riak/data/conf.yaml.example b/riak/datadog_checks/riak/data/conf.yaml.example index ddde4d09c14d5..e914c0218d7df 100644 --- a/riak/datadog_checks/riak/data/conf.yaml.example +++ b/riak/datadog_checks/riak/data/conf.yaml.example @@ -257,10 +257,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/scylla/datadog_checks/scylla/data/conf.yaml.example b/scylla/datadog_checks/scylla/data/conf.yaml.example index 3b2fa72ddb889..c67baae468c88 100644 --- a/scylla/datadog_checks/scylla/data/conf.yaml.example +++ b/scylla/datadog_checks/scylla/data/conf.yaml.example @@ -404,10 +404,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/silk/datadog_checks/silk/data/conf.yaml.example b/silk/datadog_checks/silk/data/conf.yaml.example index 0631901439de4..f0a2d39a57342 100644 --- a/silk/datadog_checks/silk/data/conf.yaml.example +++ b/silk/datadog_checks/silk/data/conf.yaml.example @@ -267,10 +267,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/sonarqube/datadog_checks/sonarqube/data/conf.yaml.example b/sonarqube/datadog_checks/sonarqube/data/conf.yaml.example index 05ea08de6d9fb..af3fb873a1163 100644 --- a/sonarqube/datadog_checks/sonarqube/data/conf.yaml.example +++ b/sonarqube/datadog_checks/sonarqube/data/conf.yaml.example @@ -347,10 +347,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/spark/datadog_checks/spark/data/conf.yaml.example b/spark/datadog_checks/spark/data/conf.yaml.example index a2fadbfef7b0a..7dc88b7723fde 100644 --- a/spark/datadog_checks/spark/data/conf.yaml.example +++ b/spark/datadog_checks/spark/data/conf.yaml.example @@ -358,10 +358,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/squid/datadog_checks/squid/data/conf.yaml.example b/squid/datadog_checks/squid/data/conf.yaml.example index 5d428e80b2a77..05a6d26983b04 100644 --- a/squid/datadog_checks/squid/data/conf.yaml.example +++ b/squid/datadog_checks/squid/data/conf.yaml.example @@ -296,10 +296,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/teamcity/datadog_checks/teamcity/data/conf.yaml.example b/teamcity/datadog_checks/teamcity/data/conf.yaml.example index a58db7b7ae67a..28ff2bbc1544c 100644 --- a/teamcity/datadog_checks/teamcity/data/conf.yaml.example +++ b/teamcity/datadog_checks/teamcity/data/conf.yaml.example @@ -290,10 +290,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/twistlock/datadog_checks/twistlock/data/conf.yaml.example b/twistlock/datadog_checks/twistlock/data/conf.yaml.example index 1cd4e410ab004..044c6807f0dd5 100644 --- a/twistlock/datadog_checks/twistlock/data/conf.yaml.example +++ b/twistlock/datadog_checks/twistlock/data/conf.yaml.example @@ -263,10 +263,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/vault/datadog_checks/vault/data/conf.yaml.example b/vault/datadog_checks/vault/data/conf.yaml.example index 8ce2a094e3711..9b063a43f8aab 100644 --- a/vault/datadog_checks/vault/data/conf.yaml.example +++ b/vault/datadog_checks/vault/data/conf.yaml.example @@ -479,10 +479,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/voltdb/datadog_checks/voltdb/data/conf.yaml.example b/voltdb/datadog_checks/voltdb/data/conf.yaml.example index cb2aa6f3de80a..dfce1c27182ba 100644 --- a/voltdb/datadog_checks/voltdb/data/conf.yaml.example +++ b/voltdb/datadog_checks/voltdb/data/conf.yaml.example @@ -158,10 +158,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/vsphere/datadog_checks/vsphere/data/conf.yaml.example b/vsphere/datadog_checks/vsphere/data/conf.yaml.example index 9289a41fc25d0..0b6b0ac6c1e15 100644 --- a/vsphere/datadog_checks/vsphere/data/conf.yaml.example +++ b/vsphere/datadog_checks/vsphere/data/conf.yaml.example @@ -594,10 +594,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false diff --git a/yarn/datadog_checks/yarn/data/conf.yaml.example b/yarn/datadog_checks/yarn/data/conf.yaml.example index e126a32f4d5c3..d53fe2ba358e6 100644 --- a/yarn/datadog_checks/yarn/data/conf.yaml.example +++ b/yarn/datadog_checks/yarn/data/conf.yaml.example @@ -337,10 +337,6 @@ instances: ## @param tls_ignore_warning - boolean - optional - default: false ## If `tls_verify` is disabled, security warnings are logged by the check. ## Disable those by setting `tls_ignore_warning` to true. - ## - ## Note: `tls_ignore_warning` set to true is currently only reliable if used by one instance of one integration. - ## If enabled for multiple instances, spurious warnings might still appear even if `tls_ignore_warning` is set - ## to true. # # tls_ignore_warning: false