From 13c4d4aa069fff22f53099b1d341f8ef10ddd5eb Mon Sep 17 00:00:00 2001
From: gibbleyg <63262871+gibbleyg@users.noreply.github.com>
Date: Thu, 22 Sep 2022 14:35:58 -0700
Subject: [PATCH] Remove custom TLS_CERTIFICATE from documentation (#596)

Remove custom TLS_CERTIFICATE from documentation

The UI does not support custom TLS_CERTIFICATE property.

If a partner requires a custom TLS_CERTIFICATE, they can add a
"certificate" STRING property and "privateKey" `MASKED_FIELD property
---
 docs/schema.md | 13 +------------
 1 file changed, 1 insertion(+), 12 deletions(-)

diff --git a/docs/schema.md b/docs/schema.md
index 7f807581..e1692f60 100644
--- a/docs/schema.md
+++ b/docs/schema.md
@@ -700,8 +700,7 @@ deployer and template can use this signal to adapt the deployment accordingly.
 
 #### type: TLS_CERTIFICATE
 
-This property provides an SSL/TLS certificate for the Kubernetes manifest. By
-default, a self-signed certificate is generated.
+This property provides a generated self-signed SSL/TLS certificate for the Kubernetes manifest.
 
 The example below shows the syntax used to declare a certificate:
 
@@ -722,16 +721,6 @@ where:
 * `base64EncodedPrivateKey` indicates the property that gets the private key.
 * `base64EncodedCertificate` indicates the property that gets the certificate.
 
-You can provide a custom certificate by overwriting the `certificate` property
-in the following JSON format:
-
-```json
-{
-  "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----",
-  "certificate": "-----BEGIN CERTIFICATE-----\n...\n-----END CERTIFICATE-----"
-}
-```
-
 If you're using a Helm chart, you can handle the certificate like this:
 
 ```yaml