-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update docs how to create a Cosmos DB for NoSQL account #814
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thank you!
* Select **Save** | ||
|
||
From here, we assume Oracle JDK 8 is properly installed in your local environment and the Azure Cosmos DB account is properly configured in Azure. | ||
1. Create Cosmos DB for NoSQL account according to the official document [Create an Azure Cosmos DB account](https://learn.microsoft.com/en-us/azure/cosmos-db/nosql/quickstart-portal#create-account) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Create Cosmos DB for NoSQL account
Create a Cosmos DB for NoSQL account
would be slightly better?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree. I updated it.
Thank you!
Note: This PR depends on PR #813.
This PR updates the steps of creating/configuring the
Cosmos DB for NoSQL
account for ScalarDB in the getting started guide.Before, the getting started guide explains concrete steps based on the Azure portal page, but there is a possibility that the UI of the portal page will be changed in the future.
So, I updated it to describe the overview of steps and add links to the official document.
This can reduce the maintenance cost of documents when the Azure portal UI is changed.
Please take a look!