Update getting-started.asciidoc #8434
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The connection should be using the cloud id and API key, not the cloud endpoint. The image unfortunately will need to be updated to as it obfuscates the cloud id and highlights the endpoint copy. This would be consistent with our docs here https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/connecting.html#cloud-deployment Which states always use the cloud id, for our Elastic Cloud Hosted deployments to connect.
|
Thanks! I pushed a commit that fixes capitalization and adds the corrected image. I also borrowed the API key phrasing from the Python client docs for now. PS: ideally this would target |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The connection should be using the cloud id and API key, not the cloud endpoint.
The image unfortunately will need to be updated to as it obfuscates the cloud id and highlights the endpoint copy.
Sample Screenshot
This would be consistent with our docs here
https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/connecting.html#cloud-deployment
Which states always use the cloud id, for our Elastic Cloud Hosted deployments to connect.