Clean up some integration config files. (DataDog#22580)

Author: nubtron

foundationdb/assets/configuration/spec.yaml

@@ -10,10 +10,9 @@ files:
     options:
     - name: cluster_file
       description: |
-        A path to the cluster file specifing connection to the FoundationDB.
+        A path to the cluster file specifying connection to the FoundationDB.
         If the check does not pass, it will rely on the binding library to find
-        the file using standard locations (e.g. `/etc/foundationdb/fdb.cluster` or
-        `/etc/foundationdb/fdb.cluster`).
+        the file using standard locations (e.g. `/etc/foundationdb/fdb.cluster`).
       fleet_configurable: true
       value:
         example: /var/lib/foundationdb/fdb.cluster
@@ -34,7 +33,7 @@ files:
       value:
         type: string
     - name: tls_password
-      description: The byte-string representing the passcode for unencrypting the private key
+      description: The byte-string representing the passcode for decrypting the private key
       fleet_configurable: true
       secret: true
       value:

foundationdb/changelog.d/22580.fixed

@@ -0,0 +1 @@
+Update configuration file descriptions.

foundationdb/datadog_checks/foundationdb/data/conf.yaml.example

@@ -15,10 +15,9 @@ instances:
 
   -
     ## @param cluster_file - string - optional - default: /var/lib/foundationdb/fdb.cluster
-    ## A path to the cluster file specifing connection to the FoundationDB.
+    ## A path to the cluster file specifying connection to the FoundationDB.
     ## If the check does not pass, it will rely on the binding library to find
-    ## the file using standard locations (e.g. `/etc/foundationdb/fdb.cluster` or
-    ## `/etc/foundationdb/fdb.cluster`).
+    ## the file using standard locations (e.g. `/etc/foundationdb/fdb.cluster`).
     #
     # cluster_file: /var/lib/foundationdb/fdb.cluster
 
@@ -38,7 +37,7 @@ instances:
     # tls_verify_peers: <TLS_VERIFY_PEERS>
 
     ## @param tls_password - string - optional
-    ## The byte-string representing the passcode for unencrypting the private key
+    ## The byte-string representing the passcode for decrypting the private key
     #
     # tls_password: <TLS_PASSWORD>
 

openldap/assets/configuration/spec.yaml

@@ -71,6 +71,7 @@ files:
                                           Don't specify this option if you want to use the same user as
                                           for the monitor backend. Set to empty string `""` for an anonymous bind.
         * `password` - string - optional: The password associated with `username`.
+      secret: true
       fleet_configurable: true
       value:
         type: array

vsphere/assets/configuration/spec.yaml

@@ -43,6 +43,7 @@ files:
       - name: use_legacy_check_version
         required: true
         display_priority: 1
+        legacy: true
         description: |
           For backward compatibility reasons, it is possible to use a deprecated version of the vSphere
           integration by setting this field to "true".
@@ -338,7 +339,7 @@ files:
             properties:
               - name: event
                 type: string
-                name: excluded_messages
+              - name: excluded_messages
                 type: array
                 items:
                   type: string

vsphere/changelog.d/22580.fixed

@@ -0,0 +1 @@
+Update configuration file.

vsphere/datadog_checks/vsphere/config_models/instance.py

@@ -37,6 +37,7 @@ class IncludeEvent(BaseModel):
         arbitrary_types_allowed=True,
         frozen=True,
     )
+    event: Optional[str] = None
     excluded_messages: Optional[tuple[str, ...]] = None