Enahance the copy as curl capability in 8.0

[lockewritesdocs]

Summary

In 8.0, security is enabled by default. We should enhance our "copy as curl" capability in code snippets to automatically include an environment variable for the auto-generated node security certificate.

Changes

In the current security documentation for 8.0, we include the following snippet so that users can test the connection to their cluster:

curl --cacert config/tls_auto_config_initial_node_<timestamp>/http_ca.crt -u elastic https://localhost:9200 

We could instead replace the location of the security in the certificate in the Elasticsearch configuration directory with an environment variable, such as $ES_CA_CERT_LOCATION, which we would instruct users to set. We also need to set https as the default connection:

curl --cacert $ES_CA_CERT_LOCATION -u elastic https://localhost:9200 

To enact this change, we would need to enhance the console widget code.

[DanRoscigno]

@lockewritesdocs what would you think about adding an environment variable for the endpoint also? I don't think I am ever targeting localhost, my target is usually a VM on my machine, or a VM in GCP, or an ECK/ECE/ESS deployment.

[lockewritesdocs]

@lockewritesdocs what would you think about adding an environment variable for the endpoint also?

This is probably more real-world applicable than localhost. I think that most folks who are running localhost are doing so in a development-only capacity.

[gtback]

@DanRoscigno if you set the endpoint in the "gear" menu in the bottom left, the new endpoint will be used when you "Copy as curl".

I don't think we could (easily) do the same thing with the cert location, though.