flyrain commented on code in PR #611: URL: https://github.com/apache/polaris/pull/611#discussion_r1902194714
########## site/content/in-dev/unreleased/configuring-polaris-for-production.md: ########## @@ -72,18 +72,54 @@ To use EclipseLink for metastore management, specify the configuration `metaStor Before using Polaris when using a metastore manager other than `in-memory`, you must **bootstrap** the metastore manager. This is a manual operation that must be performed **only once** in order to prepare the metastore manager to integrate with Polaris. When the metastore manager is bootstrapped, any existing Polaris entities in the metastore manager may be **purged**. -To bootstrap Polaris, run: +By default, Polaris will create randomised `CLIENT_ID` and `CLIENT_SECRET` for the `root` principal and store their hashes in the metastore backend. In order to provide your own credentials for `root` principal (so you can request tokens via `api/catalog/v1/oauth/tokens`), set the following envrionment variables for realm name `polaris`: Review Comment: I'd avoid using `polaris` as a realm name, since the env variable name has two `POLARIS` then. How about a name like `my_realm`? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
