chore(manifest): Re-create description fields in manifest to use Noun…

… Phrase Style
Keyfactor · Jul 3, 2024 · 3a600fb · 3a600fb
1 parent 9a9b0aa
commit 3a600fb
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 22 deletions.
diff --git a/docs/fortigate.md b/docs/fortigate.md
@@ -101,8 +101,8 @@ The following table describes the required and optional fields for the `Fortigat
 | --------- | ----------- | ------------------------- |
 | Category | Select "Fortigate" or the customized certificate store name from the previous step. | |
 | Container | Optional container to associate certificate store with. | |
-| Client Machine | For the Client Machine field, enter the IP address or DNS name of your Fortigate server. Example: '192.168.1.1' or 'fortigate.domain.com'. | |
-| Store Path | For the Store Path field, enter any value as it is not used in this integration. Example: 'NotApplicable'. | |
+| Client Machine | The IP address or DNS name of the Fortigate server. For example, '192.168.1.1' or 'fortigate.example.com'. | |
+| Store Path | Any arbitrary value, as the Store Path field is not used in the Fortigate integration. For example, 'defaultStorePath'. | |
 | Orchestrator | Select an approved orchestrator capable of managing `Fortigate` certificates. Specifically, one with the `Fortigate` capability. | |
 
 * **Using kfutil**

diff --git a/integration-manifest.json b/integration-manifest.json
@@ -1,32 +1,16 @@
 {
-    "$schema": "/Users/hroszell/coding/dev/staff-tools/keyfactor.github.io/v2/integration-manifest-schema.json",
+    "$schema": "https://keyfactor.github.io/v2/integration-manifest-schema.json",
     "integration_type": "orchestrator",
     "name": "Fortigate",
     "status": "production",
-    "description": "This integration is used to inventory and manage certificates in Fortigate.",
+    "description": "The Fortigate Universal Orchestrator extension enables remote management of cryptographic certificates on Fortigate devices, including inventory, addition, and removal of certificates.",
     "link_github": true,
     "support_level": "kf-supported",
     "update_catalog": true,
     "about": {
         "orchestrator": {
             "UOFramework": "10.1",
             "pam_support": true,
-            "win": {
-                "supportsCreateStore": false,
-                "supportsDiscovery": false,
-                "supportsManagementAdd": true,
-                "supportsManagementRemove": true,
-                "supportsReenrollment": false,
-                "supportsInventory": true
-            },
-            "linux": {
-                "supportsCreateStore": false,
-                "supportsDiscovery": false,
-                "supportsManagementAdd": true,
-                "supportsManagementRemove": true,
-                "supportsReenrollment": false,
-                "supportsInventory": true
-            },
             "store_types": [
                 {
                     "Name": "Fortigate",
@@ -51,8 +35,8 @@
                     },
                     "Properties": [],
                     "EntryParameters": [],
-                    "ClientMachineDescription": "For the Client Machine field, enter the IP address or DNS name of your Fortigate server. Example: '192.168.1.1' or 'fortigate.domain.com'.",
-                    "StorePathDescription": "For the Store Path field, enter any value as it is not used in this integration. Example: 'NotApplicable'."
+                    "ClientMachineDescription": "The IP address or DNS name of the Fortigate server. For example, '192.168.1.1' or 'fortigate.example.com'.",
+                    "StorePathDescription": "Any arbitrary value, as the Store Path field is not used in the Fortigate integration. For example, 'defaultStorePath'."
                 }
             ]
         }