Cole-Greer commented on PR #3287:
URL: https://github.com/apache/tinkerpop/pull/3287#issuecomment-3720058213

   Hi @andrii0lomakin, my apologies for the delay in getting to this PR. I 
would like to get your thoughts on a potential alternative design. If we 
allowed the server to be initialized by a list of yaml files instead of the 
current single path setup, we could gain much of the modularity of this 
"inclusion" model, without the complexity of recursive parsing, cycle 
detection, path normalization...
   
   In essence, users could launch the server in manners such as this:
   ```
   bin/gremlin.sh test-env-overrides.yaml base-config.yaml
   bin/gremlin.sh prod-env-overrides.yaml base-config.yaml
   ```
   
   Anytime there is a conflict where a single setting is defined in multiple 
files, we could give precedence to the first file listed.
   
   A "set of configs" approach is theoretically less powerful than your 
proposed "inclusion approach", however I suspect that either approach would be 
sufficient for the needs expressed in your [earlier devlist 
post](https://lists.apache.org/thread/l3f6s7khj424lpcxl8kvczpswos4rxhx).
   
   The "set of configs" approach may also lead to other benefits as it may 
allow new users a lot of flexibility to mix and match different partial configs 
which are included directly in the server distribution without needing to write 
their own config yamls. This could be useful for users experimenting with the 
server via docker, where the need to mount a volume with custom configs often 
acts as a barrier to new users. It might be nice if users could simply run 
something like this to get the exact configuration they are looking for:
   ```
   docker run tinkerpop/gremlin-server conf/tinkergraph-airroutes.yaml 
conf/ssl-enabled.yaml conf/graphson-v3.yaml
   ```


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