Currently, the Kibana client falls back to InsecureSkipVerify if the certificate is not defined in the config and the URL starts with https://. While this was fine for testing, the production code should raise an exception in such a case, navigating the user to properly configure the certificate used for communication with Kibana.
Currently, the Kibana client falls back to
InsecureSkipVerifyif the certificate is not defined in the config and the URL starts withhttps://. While this was fine for testing, the production code should raise an exception in such a case, navigating the user to properly configure the certificate used for communication with Kibana.Tracking issue for: