[I] Provide empty configuration file (`application.properties`) in the binary distribution [polaris]

["jbonofre (via GitHub)" <gi...@apache.org>]

jbonofre opened a new issue, #2686:
URL: https://github.com/apache/polaris/issues/2686

   ### Is your feature request related to a problem? Please describe.
   
   The documentation lists the useful configuration properties for Polaris: https://polaris.apache.org/releases/1.1.0/configuration/
   
   This documentation also mentions how the configuration properties can be set. Especially, it says:
   
   ```
   3. Settings in $PWD/config/application.properties file.
   ```
   
   But I think it's confusing for users regarding the binary distribution, because they actually have to create (if needed), `server/config/application.properties` and `admin/config/application.properties`.
   
   I propose:
   1. To update the documentation to clearly mention the right `application.properties` locations (in `server` and `admin`).
   2. To provide `server/config/application.properties` and `admin/config/application.properties` in the binary distribution (empty, with all properties commented).
   
   ### Describe the solution you'd like
   
   _No response_
   
   ### Describe alternatives you've considered
   
   _No response_
   
   ### 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: issues-unsubscribe@polaris.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [I] Provide empty configuration file (`application.properties`) in the binary distribution [polaris]

["harryc3139 (via GitHub)" <gi...@apache.org>]

harryc3139 commented on issue #2686:
URL: https://github.com/apache/polaris/issues/2686#issuecomment-5896950219

   Hi @jbonofre, I'd like to pick this up.
   
   Plan: ship `server/config/application.properties` and `admin/config/application.properties` in the binary distribution with everything commented out, and update the docs and distribution `README` to point to them.
   
   For contents, I would go with a short curated set plus a link to the configuration reference rather than every property, which would be hard to keep current. Roughly: `persistence/datasource` settings in both files (so admin and server use the same database), and in the server file the production-checklist items (realms, `require-header`, token broker keys) plus ports.
   
   Does that work for you, or would you prefer the full list?


-- 
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: issues-unsubscribe@polaris.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org