Version 0.4.0 is end of the line for pureharm-config it is being superseded by pureharm-config-ciris which dramatically alters the way configs are dealt with. So it's no small change. Starting with versions 0.3.0 (0.4.0 in some cases) downstream pureharm modules (e.g, db-slick, db-doobie, aws, etc) will deprecate the usage of the ConfigLoader companion objects for their configurations and encourage users to use ciris to read the configs on user side with the prefered method.

pureharm-config will still be released w/ maintenance releases, but it should be used in user-code, and will no longer be pulled in by future pureharm-modules.

The latter approach has many advantages, including easier publishing of the whole pureharm thing.

See changelog.

The available modules are:

• "com.busymachines" %% s"pureharm-config" % "0.5.0". Which has these as its main dependencies:

  • cats-effect 2.5.3
  • pureconfig 0.16.0
  • pureharm-core-anomaly 0.3.0
  • pureharm-core-sprout 0.3.0

• "com.busymachines" %% s"pureharm-config-ce2" % "0.5.0". Which has these as its main dependencies:

  • cats-effect 3.2.1
  • pureconfig 0.16.0
  • pureharm-core-anomaly 0.3.0
  • pureharm-core-sprout 0.3.0

Under construction. See release notes and tests for examples.

All code is available to you under the Apache 2.0 license, available at http://www.apache.org/licenses/LICENSE-2.0 and also in the LICENSE file.