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

DataHub

Hello! I’m running into issues when attempting to use the CLI against a deployment of datahub which uses an ingress with self-signed certs. Are there any ways to configure the CLI to not verify self-signed certs? So far my solution is to “hack” the installed CLI code and manually set `session.verify = False`, but this doesn’t seem right.

```▶ datahub ingest -c ~/Desktop/kafka.yaml                                                                                   
[2023-07-11 16:51:23,733] INFO     {datahub.cli.ingest_cli:173} - DataHub CLI version: 0.10.4.2
[2023-07-11 16:51:36,983] ERROR    {datahub.entrypoints:199} - Command failed: Failed to connect to DataHub: HTTPSConnectionPool(host='<http://my-gms.domain.com|my-gms.domain.com>', port=443): Max retries exceeded with url: /config (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1002)')))```

I did manage to get a certificate that wasn’t self signed installed, but it still might be nice if the CLI provides a config for optionally ignoring self-signed certs for those that deploy isolated, internal dev environments