Mirroristas/bigchaindb
2
0
Fork 0
mirror of https://github.com/bigchaindb/bigchaindb.git synced 2024-10-13 13:34:05 +00:00
Code Issues Packages Projects Releases Wiki Activity

User service token instead of provider key in threescale-credentials kubernetes secret (#1717)

Browse Source
This commit is contained in:
Krish 2017-08-09 10:41:51 +02:00 committed by GitHub
parent 1e06bd3aac
commit 3ce4a3d0c3
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/server/source/production-deployment-template/node-config-map-and-secrets.rst
View File

@ -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

2
k8s/configuration/secret.yaml
View File

@ -110,4 +110,4 @@ data:
secret-token: "<b64 encoded 3scale secret-token>"
service-id: "<b64 encoded 3scale service-id>"
version-header: "<b64 encoded 3scale version-header>"
provider-key: "<b64 encoded 3scale provider-key>"
service-token: "<b64 encoded 3scale service-token>"