- Add ability to define custom variables. Use
TemplateConfigBundleConfiguration.addCustomProvider(TemplateConfigVariablesProvider customProvider)
to add your custom variables provider. See the tutorial for details.
- Remove deprecated constructor
TemplateConfigBundle(java.nio.charset.Charset)
.
- 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.
- Remove deprecated constructor
TemplateConfigurationSourceProvider.TemplateConfigurationSourceProvider
.
- Method
TemplateConfigBundleConfiguration.includePath
has been replaced withTemplateConfigBundleConfiguration.resourceIncludePath
. It will be removed in 1.7.0 or 2.0.0.
-
Environment variables and system properties are now accessible without the
env.
orsys.
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.
andsys.
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. UseTemplateConfigBundleConfiguration.outputPath
to set the path to the file. It is not recommended to use this in production, as it could leak sensitive information.
- Allow inclusion of config snippets from classpath. See the tutorial for details.
-
Configuration of the bundle now uses a new configuration class. The former API has been deprecated. Please, update your code. See the docs for further details.
-
Compile against Dropwizard 0.9.2
- Constructor
TemplateConfigBundle(final Charset charset)
has been replaced with the new configuration means. It will be removed in 1.5.0 or 2.0.0.
-
make encoding of configuration template and output configurable
see https://github.com/tkrille/dropwizard-template-config#setup for how to configure this.
-
default number format not suitable for YAML output
you can now just write
${env.PORT!8080}
without having to specify the number as aString
.
- bump Freemarker to 2.3.22
- use
UTF-8
as default encoding for configuration templates
Initial Version
- write your config.yaml as a Freemarker template.