Gerrit-K opened a new issue, #1337:
URL: https://github.com/apache/polaris/issues/1337

   ### Is your feature request related to a problem? Please describe.
   
   tl;dr: it would be useful if credentials/configuration for the persistent 
metastore could be set via environment variables
   
   When running Polaris with a persistent metastore (e.g. PostgreSQL) in a 
production-like environment, it can be cumbersome to provide configuration 
details (like credentials and hostname) because they need to be embedded in raw 
in the `persistence.xml` file. In production environments, especially in the 
Kubernetes ecosystem, it is not uncommon to manage this configuration 
externally (e.g. credentials generated and managed by an operator), in which 
case the format of these configuration pieces often doesn't match the required 
`persistence.xml` format. This means that these components cannot be wired 
together using IaC, but rather some things need to be manually copied after 
deploying the metastore and embedded into a `persistence.xml`.
   
   ### Describe the solution you'd like
   
   I would be very useful if the connection details could be provided via 
environment variables - at least the URL, username and password. Ideally, this 
could be a generic solution, where the `persistence.xml` file could contain 
bash-style placeholders like `${VAR}`, which would then be replaced by 
environment variables at runtime when loading the xml file.
   
   ### Describe alternatives you've considered
   
   As a hacky workaround, we're currently injecting `initContainers` that mount 
the `persistence.xml` file, replace placeholders by environment variables and 
write the result into a new file that is then mounted by the Polaris container.
   
   ### Additional context
   
   _No response_


-- 
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]

Reply via email to