Open nik9000 opened 5 years ago
@nik9000 I think this is the Copy as cURL
issue?
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.
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:
xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.us-east-1.aws.found.io
instead of localhost
).-u user
, which will make curl prompt for the password, see https://github.com/elastic/elasticsearch/pull/31700#issuecomment-402310404.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:
In lieu of recent conversations, and the new-found knowledge that curl will prompt for the password, should we close this? or redirect it?
I believe we've done this! @nrichers, can you confirm or deny?
I'm going to repurpose this issue to track deploying this to cloud's docs. That will:
~This should be fixed by https://github.com/elastic/docs/pull/1719~ my mistake, this is unrelated.
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.