Added support for the configDrive option in the nova client

src/Compute/v2/Api.php

@@ -231,6 +231,7 @@ public function postServer(): array
                 'networks'           => $this->params->networks(),
                 'blockDeviceMapping' => $this->params->blockDeviceMapping(),
                 'keyName'            => $this->params->keyName(),
+                'configDrive'        => $this->params->configDrive(),
             ],
             'jsonKeys' => [
                 [

src/Compute/v2/Params.php

@@ -710,6 +710,17 @@ public function policy(): array
             'description' => <<<EOL
 The rules field, which is a dict, can be applied to the policy. Currently, only the max_server_per_host rule is supported for the anti-affinity policy. The max_server_per_host rule allows specifying how many members of the anti-affinity group can reside on the same compute host. If not specified, only one member from the same anti-affinity group can reside on a given host. Requesting policy rules with any other policy than anti-affinity will be 400.
 New in version 2.64
+EOL
+        ];
+    }
+
+    public function configDrive(): array
+    {
+        return [
+            'type'  => self::BOOLEAN_TYPE,
+            'sendAs' => 'config_drive',
+            'description' => <<<EOL
+Indicates whether a config drive enables metadata injection. The config_drive setting provides information about a drive that the instance can mount at boot time. The instance reads files from the drive to get information that is normally available through the metadata service. This metadata is different from the user data. Not all cloud providers enable the config_drive. 
 EOL
         ];
     }