https://datahubproject.io logo
Join Slack
Powered by
Hello all, I chatted on a few threads in <#C02QMLW...
# all-things-deployment
e
Hello all, I chatted on a few threads in #advice-data-governance, #ingestion, and #troubleshoot and have been told to bring my question here. My goal is to completely dissable UI Ingestion for all users. I tried to do so by setting the env variable 
UI_INGESTION_ENABLED
in the GMS to 
false
. That did not work. I am running v0.9.5. The exact declaration in the helm chart is below.
Copy code
datahub-gms:
  enabled: true
  image:
    repository: linkedin/datahub-gms
    tag: "v0.9.5"
  extraEnvs:
    - name: UI_INGESTION_ENABLED
      value: "false"
d
Hi Jorden, could you set managed_ingestion here to false and try it again? https://github.com/acryldata/datahub-helm/blob/master/charts/datahub/values.yaml#LL422C14-L422C14
e
That worked! Thank you @delightful-ram-75848
Nevermind. Unfortunately that also disables the env variable 
SECRET_SERVICE_ENCRYPTION_KEY
which produced an issue where no users could log in. GMS pod would return errors of 
Failed to decrypt value using provided secret
and 
javax.crypto.BadPaddingException: Given final block not properly padded. Such issues can arise if a bad key is used during decryption.
Seems out of place to have 
SECRET_SERVICE_ENCRYPTION_KEY
dependent on 
managed_ingestion
Bumping this^
Open in Slack
PreviousNext
Powered by