chore(ci): Update integration manifest

Signed-off-by: Hayden Roszell <hroszell@gmail.com>

docsource/content.md

@@ -229,22 +229,6 @@ For example, ClusterIssuer resources can be used to issue certificates for resou
         kubectl apply -f clusterissuer.yaml
         ```
 
-> **Overriding the `spec` using Kubernetes Annotations on CertificateRequest Resources** 
->
-> The 
->
-> <details><summary>Notes</summary>
-> The GoDaddy AnyCA Gateway REST plugin requires several custom enrollment parameters that are passed to GoDaddy upon the submission of a new PFX/CSR enrollment request. These custom enrollment parameters configure the domain/organization/extended validation procedure required to complete the certificate enrollment.
->
-> Prior to Command v12.3, custom enrollment parameters are not supported on a per-request basis for PFX/CSR Enrollment. If your Keyfactor Command version is less than v12.3, the only way to configure custom enrollment parameters is to set default parameter values on the Certificate Template in the Keyfactor AnyCA Gateway REST. 
->
-> Before continuing with installation prior to Command 12.3, users should consider the following:
->
-> * Each combination of custom enrollment parameters will require the creation of a new Certificate Template and Certificate Profile in the Keyfactor AnyCA Gateway REST. 
-> * If you have multiple combinations of custom enrollment parameters, consider the operational complexity of managing multiple Certificate Templates and Certificate Profiles.
-> * If your certificate workflows mostly consist of certificate renewal, re-issuance, and revocation, the GoDaddy AnyCA Gateway REST plugin is fully supported.
-> </details>
-
 # Creating a Certificate
 
 Once an Issuer or ClusterIssuer resource is created, they can be used to issue certificates using cert-manager. The two most important concepts are `Certificate` and `CertificateRequest` resources. 
@@ -341,7 +325,7 @@ Keyfactor Command allows users to [attach custom metadata to certificates](https
 
 - **Pre-defined Certificate Metadata**
 
-    If **all of the following metadata fields are defined** in Command, Command Issuer will populate the fields upon certificate enrollment. All of the metadata fields are String types. Please refer to the [Command docs](https://software.keyfactor.com/Core/Current/Content/ReferenceGuide/Certificate%20Metadata.htm) to define these metadata fields in Command.
+    If **all of the following metadata fields are defined** in Command, Command Issuer will populate the fields upon certificate enrollment. All of the metadata fields are String types. Please refer to the [Command docs](https://software.keyfactor.com/Core/Current/Content/ReferenceGuide/Certificate%20Metadata.htm) to define these metadata fields in Command if you would like Command Issuer to populate these fields on certificates upon enrollment.
 
     | Field Name                          | Description                                                                                                     |
     |-------------------------------------|-----------------------------------------------------------------------------------------------------------------|

integration-manifest.json

@@ -1,10 +1,11 @@
 {
     "$schema": "https://keyfactor.github.io/v2/integration-manifest-schema.json",
     "integration_type": "api-client",
-    "name": "command-cert-manager-issuer",
+    "name": "Command Issuer",
     "status": "production",
     "link_github": false,
     "update_catalog": false,
     "support_level": "community",
+    "platform_matrix": "linux/arm64,linux/amd64,linux/s390x,linux/ppc64le",
     "description": "cert-manager external issuer for the Keyfactor Command platform"
 }