Skip to content

Commit

Permalink
chore(manifest): Re-create description fields in manifest to use Noun…
Browse files Browse the repository at this point in the history
… Phrase Style
  • Loading branch information
m8rmclaren committed Jul 3, 2024
1 parent 2b15ee6 commit cc7527f
Show file tree
Hide file tree
Showing 4 changed files with 14 additions and 32 deletions.
4 changes: 2 additions & 2 deletions docs/f5-ca-rest.md
Original file line number Diff line number Diff line change
Expand Up @@ -214,8 +214,8 @@ The following table describes the required and optional fields for the `F5-CA-RE
| --------- | ----------- | ------------------------- |
| Category | Select "F5 CA Profiles REST" 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 server name or IP address of the F5 device you wish to manage. Ensure that the format is consistent, such as 'f5server.example.com' or '192.168.1.1'. | |
| Store Path | For the Store Path field, enter the name of the partition on the F5 device you wish to manage. This value is case-sensitive, so if the partition name is 'Common', it must be entered as 'Common' and not 'common'. | |
| Client Machine | The fully qualified domain name or IP address of the F5 device where the CA Profiles are managed. For example, 'f5.example.com' or '192.168.1.1'. | |
| Store Path | The name of the partition on the F5 device where the CA Profiles are managed, such as 'Common'. This value is case-sensitive. | |
| Orchestrator | Select an approved orchestrator capable of managing `F5-CA-REST` certificates. Specifically, one with the `F5-CA-REST` capability. | |

* **Using kfutil**
Expand Down
4 changes: 2 additions & 2 deletions docs/f5-sl-rest.md
Original file line number Diff line number Diff line change
Expand Up @@ -214,8 +214,8 @@ The following table describes the required and optional fields for the `F5-SL-RE
| --------- | ----------- | ------------------------- |
| Category | Select "F5 SSL Profiles REST" 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 server name or IP address of the F5 device you wish to manage. Ensure that the format is consistent, such as 'f5server.example.com' or '192.168.1.1'. | |
| Store Path | For the Store Path field, enter the name of the partition on the F5 device you wish to manage. This value is case-sensitive, so if the partition name is 'Common', it must be entered as 'Common' and not 'common'. | |
| Client Machine | The fully qualified domain name or IP address of the F5 device where the SSL Profiles are managed. For example, 'f5.example.com' or '192.168.1.1'. | |
| Store Path | The name of the partition on the F5 device where the SSL Profiles are managed, such as 'Common'. This value is case-sensitive. | |
| Orchestrator | Select an approved orchestrator capable of managing `F5-SL-REST` certificates. Specifically, one with the `F5-SL-REST` capability. | |

* **Using kfutil**
Expand Down
4 changes: 2 additions & 2 deletions docs/f5-ws-rest.md
Original file line number Diff line number Diff line change
Expand Up @@ -214,8 +214,8 @@ The following table describes the required and optional fields for the `F5-WS-RE
| --------- | ----------- | ------------------------- |
| Category | Select "F5 WS Profiles REST" 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 server name or IP address of the F5 device you wish to manage. Ensure that the format is consistent, such as 'f5server.example.com' or '192.168.1.1'. | |
| Store Path | For the Store Path field, enter the name of the partition on the F5 device you wish to manage. This value is case-sensitive, so if the partition name is 'Common', it must be entered as 'Common' and not 'common'. | |
| Client Machine | The fully qualified domain name or IP address of the F5 device where the Web Server (WS) Profiles are managed. For example, 'f5.example.com' or '192.168.1.1'. | |
| Store Path | The name of the partition on the F5 device where the Web Server (WS) Profiles are managed, such as 'Common'. This value is case-sensitive. | |
| Orchestrator | Select an approved orchestrator capable of managing `F5-WS-REST` certificates. Specifically, one with the `F5-WS-REST` capability. | |

* **Using kfutil**
Expand Down
34 changes: 8 additions & 26 deletions integration-manifest.json
Original file line number Diff line number Diff line change
@@ -1,35 +1,17 @@
{
"$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": "F5",
"status": "production",
"update_catalog": true,
"link_github": true,
"support_level": "kf-supported",
"release_dir": "bin/Release",
"description": "The F5 Orchestrator allows for the remote management of F5 Stores. Discovery, Inventory, and Management functions are supported.",
"description": "The F5 Universal Orchestrator extension enables remote management of cryptographic certificates within F5 devices using Keyfactor Command, supporting tasks such as inventory, certificate addition, removal, and discovery.",
"about": {
"orchestrator": {
"UOFramework": "10.1",
"pam_support": true,
"win": {
"supportsCreateStore": false,
"supportsDiscovery": true,
"supportsManagementAdd": true,
"supportsManagementRemove": true,
"supportsReenrollment": false,
"supportsInventory": true,
"platformSupport": "Unused"
},
"linux": {
"supportsCreateStore": false,
"supportsDiscovery": true,
"supportsManagementAdd": true,
"supportsManagementRemove": true,
"supportsReenrollment": false,
"supportsInventory": true,
"platformSupport": "Unused"
},
"store_types": [
{
"Name": "F5 SSL Profiles REST",
Expand All @@ -55,8 +37,8 @@
"PowerShell": false,
"BlueprintAllowed": true,
"CustomAliasAllowed": "Required",
"ClientMachineDescription": "For the Client Machine field, enter the server name or IP address of the F5 device you wish to manage. Ensure that the format is consistent, such as 'f5server.example.com' or '192.168.1.1'.",
"StorePathDescription": "For the Store Path field, enter the name of the partition on the F5 device you wish to manage. This value is case-sensitive, so if the partition name is 'Common', it must be entered as 'Common' and not 'common'."
"ClientMachineDescription": "The fully qualified domain name or IP address of the F5 device where the SSL Profiles are managed. For example, 'f5.example.com' or '192.168.1.1'.",
"StorePathDescription": "The name of the partition on the F5 device where the SSL Profiles are managed, such as 'Common'. This value is case-sensitive."
},
{
"Name": "F5 WS Profiles REST",
Expand All @@ -82,8 +64,8 @@
"PowerShell": false,
"BlueprintAllowed": true,
"CustomAliasAllowed": "Forbidden",
"ClientMachineDescription": "For the Client Machine field, enter the server name or IP address of the F5 device you wish to manage. Ensure that the format is consistent, such as 'f5server.example.com' or '192.168.1.1'.",
"StorePathDescription": "For the Store Path field, enter the name of the partition on the F5 device you wish to manage. This value is case-sensitive, so if the partition name is 'Common', it must be entered as 'Common' and not 'common'."
"ClientMachineDescription": "The fully qualified domain name or IP address of the F5 device where the Web Server (WS) Profiles are managed. For example, 'f5.example.com' or '192.168.1.1'.",
"StorePathDescription": "The name of the partition on the F5 device where the Web Server (WS) Profiles are managed, such as 'Common'. This value is case-sensitive."
},
{
"Name": "F5 CA Profiles REST",
Expand All @@ -109,8 +91,8 @@
"PowerShell": false,
"BlueprintAllowed": true,
"CustomAliasAllowed": "Required",
"ClientMachineDescription": "For the Client Machine field, enter the server name or IP address of the F5 device you wish to manage. Ensure that the format is consistent, such as 'f5server.example.com' or '192.168.1.1'.",
"StorePathDescription": "For the Store Path field, enter the name of the partition on the F5 device you wish to manage. This value is case-sensitive, so if the partition name is 'Common', it must be entered as 'Common' and not 'common'."
"ClientMachineDescription": "The fully qualified domain name or IP address of the F5 device where the CA Profiles are managed. For example, 'f5.example.com' or '192.168.1.1'.",
"StorePathDescription": "The name of the partition on the F5 device where the CA Profiles are managed, such as 'Common'. This value is case-sensitive."
}
]
}
Expand Down

0 comments on commit cc7527f

Please sign in to comment.