diff --git a/site/content/in-dev/unreleased/getting-started/quickstart.md b/site/content/in-dev/unreleased/getting-started/quickstart.md index a1a5d32df2..3ca17de4b1 100644 --- a/site/content/in-dev/unreleased/getting-started/quickstart.md +++ b/site/content/in-dev/unreleased/getting-started/quickstart.md @@ -72,7 +72,6 @@ cd ~/polaris You should see output for some time as Polaris builds and starts up. Eventually, you won’t see any more logs and should see messages that resemble the following: ``` -realm: root principal credentials: : INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) polaris-quarkus-service on JVM (powered by Quarkus ) started in 2.656s. Listening on: http://localhost:8181. Management interface listening on http://0.0.0.0:8182. INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) Profile prod activated. Live Coding activated. INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) Installed features: [...] @@ -80,20 +79,14 @@ INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) Installed features: [...] At this point, Polaris is running. -When using a Gradle-launched Polaris instance in this tutorial, we'll launch an instance of Polaris that stores entities only in-memory. This means that any entities that you define will be destroyed when Polaris is shut down. It also means that Polaris will automatically bootstrap itself with root credentials. For more information on how to configure Polaris for production usage, see the [docs]({{% relref "../configuring-polaris-for-production" %}}). - -When Polaris is launched using an in-memory metastore, the root principal credentials can be found -in stdout on initial startup. Look for a line that resembles the following: - -``` -realm: root principal credentials: : -``` - -Be sure to take note of these credentials as we'll be using them below. You can also set these credentials as environment variables for use with the Polaris CLI: +When using a Gradle-launched Polaris instance in this tutorial, we'll launch an instance of Polaris that stores entities only in-memory. This means that any entities that you define will be destroyed when Polaris is shut down. +For more information on how to configure Polaris for production usage, see the [docs]({{% relref "../configuring-polaris-for-production" %}}). +When Polaris is run using the `./gradlew run` command, the root principal credentials are `root` and `secret` for the `CLIENT_ID` and `CLIENT_SECRET`, respectively. +You can also set these credentials as environment variables for use with the Polaris CLI: ```shell -export CLIENT_ID= -export CLIENT_SECRET= +export CLIENT_ID=root +export CLIENT_SECRET=secret ``` ### Installing Apache Spark and Trino Locally for Testing