Skip to content

Commit 6a21722

Browse files
authored
Doc: Update Local Root Principal Credentials in Quickstart (#1452)
1 parent 2eb8ad4 commit 6a21722

File tree

1 file changed

+6
-13
lines changed

1 file changed

+6
-13
lines changed

site/content/in-dev/unreleased/getting-started/quickstart.md

Lines changed: 6 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -72,28 +72,21 @@ cd ~/polaris
7272
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:
7373

7474
```
75-
realm: <realm> root principal credentials: <client-id>:<client-secret>
7675
INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) polaris-quarkus-service <version> on JVM (powered by Quarkus <version>) started in 2.656s. Listening on: http://localhost:8181. Management interface listening on http://0.0.0.0:8182.
7776
INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) Profile prod activated. Live Coding activated.
7877
INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) Installed features: [...]
7978
```
8079

8180
At this point, Polaris is running.
8281

83-
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" %}}).
84-
85-
When Polaris is launched using an in-memory metastore, the root principal credentials can be found
86-
in stdout on initial startup. Look for a line that resembles the following:
87-
88-
```
89-
realm: <realm> root principal credentials: <client-id>:<client-secret>
90-
```
91-
92-
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:
82+
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.
83+
For more information on how to configure Polaris for production usage, see the [docs]({{% relref "../configuring-polaris-for-production" %}}).
9384

85+
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.
86+
You can also set these credentials as environment variables for use with the Polaris CLI:
9487
```shell
95-
export CLIENT_ID=<client-id>
96-
export CLIENT_SECRET=<client-secret>
88+
export CLIENT_ID=root
89+
export CLIENT_SECRET=secret
9790
```
9891

9992
### Installing Apache Spark and Trino Locally for Testing

0 commit comments

Comments
 (0)