A complete solution for open data platforms, enterprise data catalogs, data lakes and data management. Open source, mature, fully-featured and production ready.

DataHub

Hi All :wave:. Does anyone know what it means to get a 404 on `aspects?action=ingestProposal` when trying to delete a dataset using the CLI?

E.g.
```datahub delete --urn "urn:li:dataset:(urn:li:dataPlatform:redshift,database.schema.table,PROD)"
OperationalError: ('Unable to emit metadata to DataHub GMS', {'message': '404 Client Error: Not Found for url: <https://mydatahub.com/aspects?action=ingestProposal'}>)```

Doing a `--dry-run` does not cause any errors

My dataset metadata was ingested from the UI

hmm that looks to me like a connection issue with your GMS

are you able to run other commands using the datahub CLI?

what about `datahub ingest list-runs` for example?

Hi Aditya! That doesn't work either. This is my first time using the CLI and I assumed my connection was ok since I could `--dry-run` without errors. I have DataHub deployed in K8s with an IP-restricted ingress for the frontend. Do I need an ingress for GMS?

I would recommend doing that as well so the GMS endpoint is exposed!

I also believe the `--dry-run` command doesn’t test a GMS connection

Working now with an ingress on GMS. Thanks again Aditya! :pray:

After adding the ingress, the frontend now gets 401s from GMS when trying to ingest metadata. Any idea what I need to configure?

That is very strange. <@UV5UEC3LN> do you have any idea why this might be?

That sounds like it's stripping off the auth when routing through the ingress to GMS maybe?

Does your ingress give you details into the final request being forwarded to the GMS server? You can check the headers there and see what's being passed

Yeah it sounds something like that. I'll pull in some engineering help on my side to investigate and update here for future reference. Thanks!