This addresses something that was bothering me about who "owns" default values. The person implementing a snowplow application should not need to be an expert in what are the best config values for a specific source or sink. They might not know all the context of how the sources/sinks have been implemented and load tested. So the library should own the default values.
But I still want each value to be configurable in the app's own defaults and by the end user.
After this change, the application.conf file in snowplow applications can do things like this:
This addresses something that was bothering me about who "owns" default values. The person implementing a snowplow application should not need to be an expert in what are the best config values for a specific source or sink. They might not know all the context of how the sources/sinks have been implemented and load tested. So the library should own the default values.
But I still want each value to be configurable in the app's own defaults and by the end user.
After this change, the
application.conf
file in snowplow applications can do things like this:If a snowplow application really wants to override a particular value then it can do this in the
application.conf
file.