From 3ce4a3d0c315ad766bfab15a4286b53f39f9ae97 Mon Sep 17 00:00:00 2001 From: Krish Date: Wed, 9 Aug 2017 10:41:51 +0200 Subject: [PATCH] User service token instead of provider key in threescale-credentials kubernetes secret (#1717) --- .../node-config-map-and-secrets.rst | 2 +- k8s/configuration/secret.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/server/source/production-deployment-template/node-config-map-and-secrets.rst b/docs/server/source/production-deployment-template/node-config-map-and-secrets.rst index de7443ad..a4e8c107 100644 --- a/docs/server/source/production-deployment-template/node-config-map-and-secrets.rst +++ b/docs/server/source/production-deployment-template/node-config-map-and-secrets.rst @@ -223,7 +223,7 @@ you can delete the ``threescale-credentials`` Secret or leave all the values blank (``""``). If you *are* using 3scale, get the values for ``secret-token``, -``service-id``, ``version-header`` and ``provider-key`` by logging in to 3scale +``service-id``, ``version-header`` and ``service-token`` by logging in to 3scale portal using your admin account, click **APIs** and click on **Integration** for the relevant API. Scroll to the bottom of the page and click the small link diff --git a/k8s/configuration/secret.yaml b/k8s/configuration/secret.yaml index f27323e7..2a6992cf 100644 --- a/k8s/configuration/secret.yaml +++ b/k8s/configuration/secret.yaml @@ -110,4 +110,4 @@ data: secret-token: "" service-id: "" version-header: "" - provider-key: "" + service-token: ""