Dropwizard Template Config 1.5.0

Changelog

Features

• Add ability to define custom variables. Use
  TemplateConfigBundleConfiguration.addCustomProvider(TemplateConfigVariablesProvider customProvider)
  to add your custom variables provider. See the tutorial for details.

Changes

• Remove deprecated constructor TemplateConfigBundle(java.nio.charset.Charset).

Dropwizard Template Config 1.4.0

Changelog

Features

• Allow inclusion of config snippets from the file system. Use
  TemplateConfigBundleConfiguration.fileIncludePath(java.lang.String) to set the base include
  directory. See the tutorial for details.

Changes

• Remove deprecated constructor TemplateConfigurationSourceProvider.TemplateConfigurationSourceProvider.

Deprecations

• Method TemplateConfigBundleConfiguration.includePath has been replaced with
  TemplateConfigBundleConfiguration.resourceIncludePath. It will be removed
  in 1.7.0 or 2.0.0.

Dropwizard Template Config 1.3.0

Changelog

Features

• Environment variables and system properties are now accessible without the env. or sys. prefixes.
  So instead of writing ${env.PORT} you can now just write ${PORT}.
  Environment variables overwrite system properties, if they have the same name.
  env. and sys. are still supported for backwards compatibility and to access system properties
  with special characters in their name.
• Write the rendered config.yaml to a file for debugging and testing.
  Use TemplateConfigBundleConfiguration.outputPath to set the path to the file.
  It is not recommended to use this in production, as it could leak sensitive information.