[FA] Onboard more integrations (DataDog#22568)

* Add iboss

* Add openstack

* Add ossec_security

* Add tekton

* Add varnish

* Add suricata

* Add foundationdb

* Add glusterfs

Author: coignetp

foundationdb/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: FoundationDB
+fleet_configurable: true
 files:
 - name: foundationdb.yaml
   options:
@@ -13,33 +14,40 @@ files:
         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`).
+      fleet_configurable: true
       value:
         example: /var/lib/foundationdb/fdb.cluster
         type: string
     - name: tls_certificate_file
       description: Path to the file from which the local certificates can be loaded
+      fleet_configurable: true
       value:
         type: string
     - name: tls_key_file
       description: Path to the file from which to load the private key
+      fleet_configurable: true
       value:
         type: string
     - name: tls_verify_peers
       description: The byte-string for the verification of peer certificates and sessions
+      fleet_configurable: true
       value:
         type: string
     - name: tls_password
       description: The byte-string representing the passcode for unencrypting the private key
+      fleet_configurable: true
       secret: true
       value:
         type: string
     - name: tls_ca_file
       description: Path to the file containing the CA certificates to trust
+      fleet_configurable: true
       value:
         type: string
     - name: custom_queries
       description: |
         Define custom queries to collect custom metrics from your FoundationDB
+      fleet_configurable: true
       value:
         type: array
         items:

glusterfs/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: GlusterFS
+fleet_configurable: true
 files:
 - name: glusterfs.yaml
   options:
@@ -10,6 +11,7 @@ files:
 
         A version of the gstatus is shipped with the Agent binary.
         If you are using a source install, specify the location of gstatus.
+      fleet_configurable: true
       value:
         type: string
         example: <datadog-agent>/embedded/sbin/gstatus
@@ -23,6 +25,7 @@ files:
         dd-agent ALL=(ALL) NOPASSWD:<datadog-agent>/embedded/sbin/gstatus
 
         Enable the option for the check to run with sudo.
+      fleet_configurable: true
       value:
         type: boolean
         example: true

iboss/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: iboss
+fleet_configurable: true
 files:
 - name: iboss.yaml
   options:

openstack/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: OpenStack
+fleet_configurable: true
 
 files:
   - name: openstack.yaml
@@ -7,6 +8,7 @@ files:
       - template: init_config
         options:
           - name: keystone_server_url
+            fleet_configurable: true
             required: true
             description: |
               Where your identity server lives. Note that the server must support Identity API v3
@@ -86,6 +88,7 @@ files:
       - template: instances
         options:
           - name: name
+            fleet_configurable: true
             required: true
             description: |
               Unique identifier for this instance.

ossec_security/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: ossec-security
+fleet_configurable: true
 files:
 - name: ossec_security.yaml
   options:

suricata/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: suricata
+fleet_configurable: true
 files:
 - name: suricata.yaml
   options:

tekton/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: Tekton
+fleet_configurable: true
 files:
 - name: tekton.yaml
   options:
@@ -10,6 +11,7 @@ files:
     - name: pipelines_controller_endpoint
       description: |
         Endpoint exposing the Pipelines Controller's Prometheus metrics.
+      fleet_configurable: true
       value:
         display_default: null
         example: http://tekton-pipelines-controller:9090/metrics

varnish/assets/configuration/spec.yaml

@@ -1,4 +1,5 @@
 name: Varnish
+fleet_configurable: true
 files:
   - name: varnish.yaml
     options:
@@ -8,6 +9,7 @@ files:
       - template: instances
         options:
           - name: varnishstat
+            fleet_configurable: true
             required: true
             description: |
               The full path to the varnishstat binary and can contain additional arguments.
@@ -29,6 +31,7 @@ files:
               Version 4.1.7 has been released and includes a fix for this.
               Using the exclusion blob with a broken version silences the integration.
               However, you can still use the inclusion blob with those versions.
+            fleet_configurable: true
             value:
               type: array
               items:
@@ -39,6 +42,7 @@ files:
             description: |
               The name used in the varnishstat command for the
               -n argument which will add a name:<INSTANCE_NAME> tag to all metrics.
+            fleet_configurable: true
             value:
               type: string
               example: <INSTANCE_NAME>
@@ -50,26 +54,30 @@ files:
               in order to support service discovery.
 
               The service check is tagged by backend.
+            fleet_configurable: true
             value:
               type: string
               example: /usr/bin/varnishadm
               display_default: null
           - name: secretfile
             description: The path to the varnish secretfile used in the varnishadm command, if enabled.
+            fleet_configurable: true
             value:
               type: string
               example: /etc/varnish/secret
           - name: daemon_host
             description: |
               The parameters for specifying the host to connect to varnishadm.
               Used in version 4.1.0 and above.
+            fleet_configurable: true
             value:
               type: string
               example: localhost
           - name: daemon_port
             description: |
               The parameters for specifying the port to connect to varnishadm.
               Used in version 4.1.0 and above.
+            fleet_configurable: true
             value:
               type: integer
               example: 6082