From 8652de1aac989da005ddd50c56f15be9c5f62f6e Mon Sep 17 00:00:00 2001 From: Ronald Angel Date: Thu, 5 May 2022 00:33:33 +0200 Subject: [PATCH] fix(docs): fix the metadata service auth documentation and frontend clarifications (#4722) --- docs/deploy/aws.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/docs/deploy/aws.md b/docs/deploy/aws.md index a8e5fe1a5c..ff9d7e6345 100644 --- a/docs/deploy/aws.md +++ b/docs/deploy/aws.md @@ -162,6 +162,14 @@ You need to request a certificate in the AWS Certificate Manager by following th the ARN of the new certificate. You also need to replace host-name with the hostname of choice like demo.datahubproject.io. +To have the metadata [authentication service](https://datahubproject.io/docs/introducing-metadata-service-authentication/#configuring-metadata-service-authentication) enable and use [API tokens](https://datahubproject.io/docs/introducing-metadata-service-authentication/#generating-personal-access-tokens) from the UI you will need to set the configuration in the values.yaml for the `gms` and the `frontend` deployments. This could be done by enabling the `metadata_service_authentication`: + +``` +datahub: + metadata_service_authentication: + enabled: true +``` + After updating the yaml file, run the following to apply the updates. ``` @@ -467,4 +475,4 @@ acryl-datahub-actions: serviceAccount: name: <> ... -``` \ No newline at end of file +```