- Add
loadConfigParser()helper that returns aCerebroparser instance that is used to generate aCerebroConfiginstance.
- Add
getConfigValueForLabel()method toCerebroConfig
- Cherry-picked polling feature from
cerebroby @juandopazo
Contributor: Theo Gravity
- Fix npm audit issues
- New generics definitions
Breaking changes:
- The generics for
CerebroConfigand related interfaces have changed.
See the MIGRATING.md file for more information.
Contributor: Theo Gravity
- Update README.md
Fix npm badge from http->https to fix render issues on the npm page
Contributor: Theo Gravity
- Updated readme on getRawConfig()
A note has been added that getRawConfig() does not deep clone the object.
Contributor: Theo Gravity
- Add getAssertValue(), Remove type-specific getters (#2)
Type-specific getters turned out to be unnecessary as the YAML parser already does proper type conversion internally.
I was unable to justify keeping them as a result, and removed them to simplify the API.
A new method, getAssertValue(), was added to ensure a value exists, and throw if it does not.
Due to the removal of the type-specific getters, the package major version has been updated.
Contributor: Theo Gravity
- Add
getConfigForLabel()
In cerebro, you can assign tags (it calls them labels) to settings to group settings under a particular tag.
Although it could do this, its usage was very limited as it does not have a getter to work with them.
The new method allows you to get a set of settings by its tag.
Contributor: Theo Gravity
- Rename package from
prod-config->configurity
Thanks to reddit user sieabah for the suggestion.
Contributor: Theo Gravity
-
First version
-
Define configuration using a YAML file (you can still use the original
Cerebroobject if you want to use JSON) -
environment variable overrides
-
Incorporates AND of settings by @lpw
-
Updated parts of the codebase to Typescript
-
Updated parts of the codebase to classes
-
Updated toolchain to be typescript-based
-
Added new methods to the config object
-
Re-written readme / updated usage examples to use the YAML format instead