Hey Team, I want to run an ingestion of a policies...
# ingestion
e
Hey Team, I want to run an ingestion of a policies file to replace the default policies of datahub at
/datahub/datahub-gms/resources/policies.json
however the ingestion-cron pod can't find that path. Recipe file looks like this
Copy code
source:
  type: file
  config:
    # Coordinates
    filename: ../policies.json

sink:
  type: file
  config:
    filename: /datahub/datahub-gms/resources/policies.json
I am trying to remove the permission of
MANAGE_INGESTION
from all users as to totally disable UI ingestion.
1
🔍 1
📖 1
l
Hey there 👋 I'm The DataHub Community Support bot. I'm here to help make sure the community can best support you with your request. Let's double check a few things first: ✅ There's a lot of good information on our docs site: www.datahubproject.io/docs, Have you searched there for a solution? ✅ button ✅ It's not uncommon that someone has run into your exact problem before in the community. Have you searched Slack for similar issues? ✅ button Did you find a solution to your issue? ❌ Sorry you weren't able to find a solution. I'm sending you some tips on info you can provide to help the community troubleshoot. Whenever you feel your issue is solved, please react ✅ to your original message to let us know!
g
Hi @elegant-nightfall-29115 Could you please share document you are following to do this update ? As per my understanding the policy file is bundled inside the GMS war file and it is non editable
e
Hey @gentle-hamburger-31302 I couldn't find any documentation about changing default policies on the Datahub website. But I found this thread in here where @big-carpet-38439 seemed to suggest I could handle policies by using the Datahub Ingest CLI in this comment here
g
Ok, I believe in your recipe the Sink should DataHub Sink and ../policies.json should contain the MCP
e
What should the MCP look like as this is a policy change not a dataset or chart metadata change?
g
Hi @elegant-nightfall-29115 As discussed on tread thread please raise the issue on #all-things-deployment