Synchronize configuration files with the spec changes

celerdata/datadog_checks/celerdata/data/conf.yaml.example

@@ -398,6 +398,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -476,8 +481,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

cloudnatix/datadog_checks/cloudnatix/data/conf.yaml.example

@@ -385,6 +385,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -463,8 +468,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

cyral/datadog_checks/cyral/data/conf.yaml.example

@@ -339,6 +339,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -417,8 +422,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

emqx/datadog_checks/emqx/data/conf.yaml.example

@@ -427,6 +427,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -505,8 +510,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

eventstore/datadog_checks/eventstore/data/conf.yaml.example

@@ -232,6 +232,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -310,8 +315,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

filebeat/datadog_checks/filebeat/data/conf.yaml.example

@@ -276,6 +276,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -354,8 +359,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

fluentbit/datadog_checks/fluentbit/data/conf.yaml.example

@@ -427,6 +427,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -505,8 +510,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

gatekeeper/datadog_checks/gatekeeper/data/auto_conf.yaml

@@ -313,6 +313,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -391,8 +396,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

gatekeeper/datadog_checks/gatekeeper/data/conf.yaml.example

@@ -344,6 +344,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -422,8 +427,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

gitea/datadog_checks/gitea/data/auto_conf.yaml

@@ -396,6 +396,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -474,8 +479,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

gitea/datadog_checks/gitea/data/conf.yaml.example

@@ -427,6 +427,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -505,8 +510,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

gnatsd/datadog_checks/gnatsd/data/conf.yaml.example

@@ -214,6 +214,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -292,8 +297,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

gnatsd_streaming/datadog_checks/gnatsd_streaming/data/conf.yaml.example

@@ -209,6 +209,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -287,8 +292,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

hikaricp/datadog_checks/hikaricp/data/conf.yaml.example

@@ -427,6 +427,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -505,8 +510,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

kernelcare/datadog_checks/kernelcare/data/conf.yaml.example

@@ -223,6 +223,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -301,8 +306,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

logstash/datadog_checks/logstash/data/conf.yaml.example

@@ -205,6 +205,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -283,8 +288,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>
 

neo4j/datadog_checks/neo4j/data/conf.yaml.example

@@ -399,6 +399,11 @@ instances:
  ## client_secret (required): The client secret.
  ## basic_auth: Whether the provider expects credentials to be transmitted in
  ## an HTTP Basic Auth header. The default is: false
+ ## options: Mapping of additional options to pass to the provider, such as the audience
+ ## or the scope. For example:
+ ## options:
+ ## audience: https://example.com
+ ## scope: read:example
  ##
  ## The available writers are:
  ##
@@ -477,8 +482,8 @@ instances:
  ## @param tls_ca_cert - string - optional
  ## The path to a file of concatenated CA certificates in PEM format or a directory
  ## containing several CA certificates in PEM format. If a directory, the directory
- ## must have been processed using the c_rehash utility supplied with OpenSSL. See:
- ## https://www.openssl.org/docs/manmaster/man3/SSL_CTX_load_verify_locations.html
+ ## must have been processed using the `openssl rehash` command. See:
+ ## https://www.openssl.org/docs/man3.2/man1/c_rehash.html
  #
  # tls_ca_cert: <CA_CERT_PATH>