OPEN IN CONSOLE should work against cloud!

[nik9000]

I've just been told that the OPEN IN CONSOLE links don't work properly against cloud. That is terrible! We should make super sure that you can use cloud.

[nrichers]

@nik9000 I think this is the Copy as cURL issue?

[nik9000]

I think we should make a way to trigger "cloud API" snippets and then build "copy as curl" for them. Console just isn't designed to work against anything but the Elasticsearch API so it might never support talking directly to cloud. But we'd get a nice copy-as-curl thing for these.

[nik9000]

See also: elastic/elasticsearch#31700

[nrichers]

The relevant bit from elastic/elasticsearch#31700:

The COPY AS CURL button used in the getting started section doesn't work against our hosted Elasticsearch Service as is, with no way to change that. To make our hosted Elasticsearch Service a viable alternative for people trying out these getting started steps, we would need:

• A way to configure the COPY AS CURL button to use ES endpoints on Cloud (e.g. xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.us-east-1.aws.found.io instead of localhost).
• Support for HTTPS endpoints. We strong recommend HTTPS and some regions don't support HTTP (e.g. Frankfurt).
• A way to tell people that they also need to authenticate with -u elastic: when running these curl commands. (I don't think we want to let people save their elastic superuser PW in the docs console to do it for them, so this adds a manual step for every example command.)
  EDIT: Panos' suggestion was to simply use -u user, which will make curl prompt for the password, see WIP Add a pointer to our hosted ES service elasticsearch#31700 (comment).

On the upside, the current configuration modal lets you set the Kibana endpoint, which works just fine against Cloud when I tested it just now:

[haywoood]

In lieu of recent conversations, and the new-found knowledge that curl will prompt for the password, should we close this? or redirect it?

[nik9000]

I believe we've done this! @nrichers, can you confirm or deny?

[nik9000]

I'm going to repurpose this issue to track deploying this to cloud's docs. That will:

1. Come after converting cloud's docs to Asciidoctor.
2. Require some engineering to separate the configuration of the "coordinating" server (ECE) from the cloud endpoint (SaaS).

[nyurik]

This should be fixed by #1719 my mistake, this is unrelated.