Skip to content

Update Local Root Principal Credentials in Quickstart #1452

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Apr 25, 2025
Merged

Update Local Root Principal Credentials in Quickstart #1452

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ca598bd
Update Local Root Principal Credentials in Quickstart
adnanhemani Apr 24, 2025
5525386
Refactor
adnanhemani Apr 25, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 6 additions & 13 deletions site/content/in-dev/unreleased/getting-started/quickstart.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,28 +72,21 @@ 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: <realm> root principal credentials: <client-id>:<client-secret>
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.
INFO [io.quarkus] [,] [,,,] (Quarkus Main Thread) Profile prod activated. Live Coding activated.
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: <realm> root principal credentials: <client-id>:<client-secret>
```

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=<client-id>
export CLIENT_SECRET=<client-secret>
export CLIENT_ID=root
export CLIENT_SECRET=secret
```

### Installing Apache Spark and Trino Locally for Testing
Expand Down