docs(secret-management) update secret management docs for GA

.github/styles/kong/dictionary.txt

@@ -85,6 +85,7 @@ JsonPath
 jwk
 jwks
 jwt
+kafka
 Keycloak
 keyspace
 kiali

app/_hub/kong-inc/acme/_index.md

@@ -37,8 +37,8 @@ params:
         The account identifier. Can be reused in a different plugin instance.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: api_uri
       required: false
       default: '` https://acme-v02.api.letsencrypt.org/directory`'
@@ -114,8 +114,8 @@ params:
         External account binding (EAB) key id. You usually don't need to set this unless it is explicitly required by the CA.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: eab_hmac_key
       minimum_version: "2.4.x"
       required: false
@@ -125,8 +125,8 @@ params:
         External account binding (EAB) base64-encoded URL string of the HMAC key. You usually don't need to set this unless it is explicitly required by the CA.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: rsa_key_size
       minimum_version: "2.8.x"
       required: false

app/_hub/kong-inc/aws-lambda/_index.md

@@ -39,8 +39,8 @@ params:
         is configured.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: aws_secret
       required: semi
       value_in_examples: <AWS_SECRET>
@@ -56,8 +56,8 @@ params:
         is configured.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: aws_region  # old version, do not update
       maximum_version: "2.5.x"
       required: true
@@ -128,8 +128,8 @@ params:
         used for a cross-account Lambda function invocation.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: aws_role_session_name
       minimum_version: "2.8.x"
       required: false

app/_hub/kong-inc/azure-functions/_index.md

@@ -1,7 +1,6 @@
 ---
 name: Azure Functions
 publisher: Kong Inc.
-source_url: 'https://github.com/Kong/kong-plugin-azure-functions'
 desc: Invoke and manage Azure functions from Kong
 description: |
   This plugin invokes
@@ -60,8 +59,8 @@ params:
         The apikey to access the Azure resources. If provided, it is injected as the `x-functions-key` header.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: clientid
       required: false
       default: null
@@ -72,8 +71,8 @@ params:
         The `clientid` to access the Azure resources. If provided, it is injected as the `x-functions-clientid` header.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: https_verify
       required: false
       default: false

app/_hub/kong-inc/forward-proxy/_index.md

@@ -132,8 +132,8 @@ params:
         by basic authentication.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: auth_password
       required: false
       default: null
@@ -144,8 +144,8 @@ params:
         by basic authentication.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: https_verify
       required: true
       default: false
@@ -178,7 +178,7 @@ params:
 * The `auth_password` and `auth_username` configuration fields are now marked as
 referenceable, which means they can be securely stored as
 [secrets](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
 
 * Fixed a plugin version in the documentation. Previously, there was a plugin
 version labelled as `1.0.x`. It is now updated to align with the

app/_hub/kong-inc/graphql-rate-limiting-advanced/_index.md

@@ -179,8 +179,8 @@ params:
         If undefined, ACL authentication will not be performed. This requires Redis v6.0.0+.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
       minimum_version: "2.8.x"
     - name: redis.password
       required: semi
@@ -192,8 +192,8 @@ params:
         If undefined, no AUTH commands are sent to Redis.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: redis.database
       required: semi
       default: 0
@@ -218,8 +218,8 @@ params:
         If undefined, ACL authentication will not be performed. This requires Redis v6.2.0+.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
       minimum_version: "2.8.x"
     - name: redis.sentinel_password
       required: semi
@@ -231,8 +231,8 @@ params:
         If undefined, no AUTH commands are sent to Redis Sentinels.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: redis.sentinel_role
       required: semi
       default: null
@@ -689,7 +689,7 @@ curl -i -X PATCH http://kong:8001/plugins/{plugin_id} \
 * The `redis.username`, `redis.password`, `redis.sentinel_username`, and `redis.sentinel_password`
 configuration fields are now marked as referenceable, which means they can be securely stored as
 [secrets](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
 
 * Fixed plugin versions in the documentation. Previously, the plugin versions
 were labelled as `1.3-x` and `2.3.x`. They are now updated to align with the

app/_hub/kong-inc/kafka-log/_index.md

@@ -70,8 +70,8 @@ params:
         Username for SASL authentication.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: authentication.password
       required: false
       value_in_examples: admin-secret
@@ -83,8 +83,8 @@ params:
         Password for SASL authentication.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: authentication.tokenauth
       required: false
       value_in_examples: false
@@ -313,7 +313,7 @@ Known limitations:
 
 ## Changelog
 
-### Kong Gateway 2.8.x (plugin version 0.4.0)
+**{{site.base_gateway}} 2.8.x**
 
 * Added support for the `SCRAM-SHA-512` authentication mechanism.
 
@@ -322,9 +322,9 @@ Known limitations:
 * The `authentication.user` and `authentication.password` configuration fields are now marked as
 referenceable, which means they can be securely stored as
 [secrets](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
 
-### Kong Gateway 2.7.x (plugin version 0.3.0)
+**{{site.base_gateway}} 2.7.x**
 
 * Starting with {{site.base_gateway}} 2.7.0.0, if keyring encryption is enabled,
  the `config.authentication.user` and `config.authentication.password` parameter

app/_hub/kong-inc/kafka-upstream/_index.md

@@ -72,8 +72,8 @@ params:
         Username for SASL authentication.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: authentication.password
       required: false
       value_in_examples: admin-secret
@@ -85,8 +85,8 @@ params:
         Password for SASL authentication.
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: authentication.tokenauth
       required: false
       value_in_examples: false
@@ -376,7 +376,7 @@ The following steps assume that {{site.base_gateway}} is installed and the Kafka
 
 ## Changelog
 
-### Kong Gateway 2.8.x (plugin version 0.4.0)
+**{{site.base_gateway}} 2.8.x**
 
 * Added support for the `SCRAM-SHA-512` authentication mechanism.
 
@@ -385,9 +385,9 @@ The following steps assume that {{site.base_gateway}} is installed and the Kafka
 * The `authentication.user` and `authentication.password` configuration fields are now marked as
 referenceable, which means they can be securely stored as
 [secrets](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
 
-### Kong Gateway 2.7.x (plugin version 0.3.0)
+**{{site.base_gateway}} 2.7.x**
 
 * Starting with {{site.base_gateway}} 2.7.0.0, if keyring encryption is enabled,
  the `config.authentication.user` and `config.authentication.password` parameter

app/_hub/kong-inc/ldap-auth-advanced/_index.md

@@ -318,7 +318,7 @@ mapping.
 * The `ldap_password` and `bind_dn` configuration fields are now marked as
 referenceable, which means they can be securely stored as
 [secrets](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
 
 **{{site.base_gateway}} 2.7.x**
 

app/_hub/kong-inc/loggly/_index.md

@@ -48,8 +48,8 @@ params:
         Loggly [customer token](https://www.loggly.com/docs/customer-token-authentication-token/).
 
         This field is _referenceable_, which means it can be securely stored as a
-        [secret](/gateway/latest/plan-and-deploy/security/secrets-management/getting-started)
-        in a vault. References must follow a [specific format](/gateway/latest/plan-and-deploy/security/secrets-management/reference-format).
+        [secret](/gateway/latest/kong-enterprise/security/secrets-management/getting-started)
+        in a vault. References must follow a [specific format](/gateway/latest/kong-enterprise/security/secrets-management/reference-format).
     - name: tags
       required: false
       default: '`kong`'