@codedv8/dynamicconfig
v2.8.0
Published
Dynamic configuration storage that can use files and/or environment. Different sets of configuration can be used. Configuration files can have a fallback configuration file. Getting values from the configuration can have a default value or can throw an er
Downloads
34
Maintainers
Readme
DynamicConfig
Dynamic configuration storage that can use files and/or environment.
Different sets of configuration can be used.
If present, a default configuration file will always be merged without overwriting previous data.
Installation
Installing from NPM
npm install @codedv8/dynamicconfig --save
Installing from GitHub
npm install https://github.com/codedeviate/dynamicconfig.git --save
Typescript
Batteries are included.
This module contains a typescript declaration.
Fused entries
Keys can be protected by a fuse.
A fused key can't have its value changed by calling the set function.
After calling the function setBlowOnFuse any attempt to set a fused value will result in throwing an exception. This value can not be unset.
const dynConf = require('@codedv8/dynamicconfig');
...
dynConf.addFuse('fused.value');
...
dynConf.set('fused.value', 'new value');
This will result in throwing an exception.
const dynConf = require('@codedv8/dynamicconfig');
...
dynConf.addFuse('fused.value');
...
dynConf.set('fused.value', 'new value');
This will just return quietly without changing any values.
Fallback and default configuration
First of all a configuration matching the enviroment will be loaded. After that the module will search for a default configuration that will be merged without overwriting existing data.
Usage
Force type of config
CONFIG_TYPE=ini node example/basic.js
This will only use files with an ini extention
Set execution environment
NODE_ENV=development node example/basic.js
This will use a config files named development.*. If none is found it will still try to find a config file named default.*.
Set execution environment and force type of config
NODE_ENV=development CONFIG_TYPE=json node example/basic.js
This will use a config files named development.json. If none is found it will still try to find a config file named default.json.
Code usage
Output the current configuration
const devConf = require('@codedv8/dynamicconfig');
console.log(JSON.stringify(devConf.get(), null, ' '));
Get PORT with default value 3070
const devConf = require('@codedv8/dynamicconfig');
const PORT = devConf.get('PORT', 3070);
Get and set values without fuse and with fuse
const devConf = require('@codedv8/dynamicconfig');
console.log('PORT :', devConf.get('PORT', 3070));
devConf.set('PORT', 3071);
console.log('PORT :', devConf.get('PORT', 3070));
devConf.addFuse('PORT');
console.log('PORT :', devConf.get('PORT', 3070));
devConf.set('PORT', 3072);
console.log('PORT :', devConf.get('PORT', 3070));
This will print
PORT : 3070
PORT : 3071
PORT : 3071
PORT : 3071
Get and set values without fuse and with fuse where fuses are set to blow
const devConf = require('@codedv8/dynamicconfig');
devConf.setBlowOnFuse();
console.log('PORT :', devConf.get('PORT', 3070));
devConf.set('PORT', 3071);
console.log('PORT :', devConf.get('PORT', 3070));
devConf.addFuse('PORT');
console.log('PORT :', devConf.get('PORT', 3070));
devConf.set('PORT', 3072);
console.log('PORT :', devConf.get('PORT', 3070));
This will print
PORT : 3070
PORT : 3071
PORT : 3071
/xxxx/xxxx/xxxx/dynamicconfig/index.js:XXX
throw new Error(`Key ${key} is fused`);
^
Error: Key PORT is fused
...
Examples in TypeScript
Get PORT with default value 3070
import devConf from '@codedv8/dynamicconfig'
const PORT = devConf.get('PORT', 3070)
Functions
get(key, defaultValue = null, throwOnDefault = false): value
Will try to find the key from the environment or the config (in that order). If the key isn't found then the default value will be returned. If not default value has been supplied then null will be retruned.
If the parameter throwOnDefault is set to true then an exception will be thrown if the key isn't found.
If the key is omitted (or set to undefined) the config object wil be returned.
If key is an array then the function will return the value for the first subKey that exists.
getAsString(key, defaultValue = "", throwOnDefault = false): value
The same as get but returns a string.
NULL will be returned as an empty string.
If key is an array then the function will return the value for the first subKey that exists.
getAsInt(key, defaultValue = "", throwOnDefault = false): int
The same as get but returns the value as an integer.
- NULL will be returned as 0
- false will be returned as 0
- true will be returned as 1
If key is an array then the function will return the value for the first subKey that exists.
getAsFloat(key, defaultValue = "", throwOnDefault = false): float
The same as get but returns the value as a float.
- NULL will be returned as 0
- false will be returned as 0
- true will be returned as 1
If key is an array then the function will return the value for the first subKey that exists.
getAsBoolean(key, defaultValue = "", throwOnDefault = false): boolean
The same as get but returns the value as a boolean.
- NULL will be returned as false
- "null", "false", "0" will be returned as false
If key is an array then the function will return the value for the first subKey that exists.
getConfig(key, defaultValue = null): [value, keyFound]
Will try to find the key in the config.
The return value is an array where the first value is the values that is returned. The second value is a boolean that indicated if the value was found or not.
getEnv(key, defaultValue = null): [value, keyFound]
Will try to find the key in the environment.
The return value is an array where the first value is the values that is returned. The second value is a boolean that indicated if the value was found or not.
has(key): boolean
Returns a boolean that indicates if the key can be found in either the environment or the config.
If key is an array then the function will return true for the first subKey that exists or false if none matches.
hasConfig(key): boolean
Returns a boolean that indicates if the key can be found in the config.
hasEnv(key): boolean
Returns a boolean that indicates if the key can be found in the environment.
set(key, value)
Sets a key in the config to the supplied value
is(key, value): boolean
This will test if the key is equal to the given value and return true or false.
If key is an array then the function will return true for the first subKey that matches the given value or false if none matches.
isNot(key, value): boolean
This will test if the key differs from the the given value and return true or false.
If key is an array then the function will return false if any of the subKeys matches the given value it true if none matches.
envPopulate(key)
Will copy the settings found under the supplied key to process.env making them accessible for other parts of the system.
Keys that already exists in process.env will not be overwritten.
If the value for the supplied key is an object then this object will be iterated and subkeys and their respective values will be added. Otherwise the value for the supplied key will be used with the key name.
addFuse(key)
Will create a fuse for the supplied key
If multiple arguments is supplied then fuses will be created for these keys as well.
If an array is supplied as an argument then the values of this array will be used as keys to fuse.
fuseAll()
Will create a fuse for all keys in the config.
listFuseable(callback)
Will loop through the config and call the callback with the key for this entry making it possible to call addFuse for specific entries.
setBlowOnFuse()
Will set the internal flag to true which will throw an exception when trying to alter an existing entry.
blowOnFuse(): boolean
Returns true if an exception will be thrown when trying to set a fused key.
Returns false if set will return quietly when trying to set a fused key.
setConfiguration(object)
Set the entire configuration object.
If the new configuration contain any fused entries it will be the same as setting an fused entry.
If the setting of a new object fails due to fused values then the entire configuration will be reverted back to the previous state.
mergeConfiguration(object)
Merge a configuration without overwriting existing values.
getSplit(): string
Get the split character used for get and set
setSplit(delimiter)
Set the split character used for get and set
chain(): DynamicChain
This will create a new chainable object
class DynamicChain
This is a chainable object that is connected to the config object. With this object you can perform logical operation and get a boolean result based on these operations.
reset(): DynamicChain
This will reset the internal chaining result.
is(key, value): DynamicChain
This will make an AND with the internal chaining result and the result if the key has the given value.
isNot(key, value): DynamicChain
This will make an AND with the internal chaining result and the result if the key has not the given value.
hasKey(key): DynamicChain
This will make an AND with the internal chaining result and if the key exist.
hasNotKey(key): DynamicChain
This will make an AND with the internal chaining result and if the key does not exist.
result(): boolean
This will return the current value of the internal chaining result
Multiple keys
For the following functions it is possible to use an array of strings as the key.
- get
- getAsString
- getAsInt
- getAsFloat
- getAsBoolean
- has
- is
- isNot
When using an array as the key the function will treat it as a series of calls and return a response on the first key found. The exception is isNot where all the keys must not match.
Please note that the following functions doesn't support keys as arrays
- getConfig
- getEnv
- hasConfig
- hasEnv
Potential use cases for multiple keys
You could rewrite the code for an array by using default values
const unreadable = config.get("test", config.get("test2", config.get("test3")))
this can now be written as
const readable = config.get(["test", "test2", "test3"])
If you need to throw an exception if a value isn't found after attempting to find several keys it will be a much cleaner code using an array.
let unreadable = config.get("test");
if(unreadable === null) {
unreadable = config.get("test2");
if(unreadable === null) {
config.get("test3", null, true)
}
}
this can now be written as
const readable = config.get(["test", "test2", "test3"], null, true)
The following code
if(config.get("test1") === "value" || config.get("test2") === "value" || config.get("test3") === "value") {
// Do something
}
can be reduced to this
if(config.is(["test1", "test2", "test3"], "value") {
// Do something
}
Multiple keys in chains
The following functions supports multiple keys
- is
- isNot
- hasKey
- hasNotKey
For the is and hasKey functions the order of apperance for the keys in the array will be the order of priority for which key returns the result. Only the result from the first matching key will be returned.
For the isNot and hasNotKey all keys must meet the condition.
Numeric vs string based keys
If the key is numeric it can not use used as a key for sections. To be able to use sections the key has to be supplied as a string.
The key 5 and the key "5" will yield the same result but both keys will be treated differently by the code. There will be an attempt to split the string key into parts referencing sections in the config. The numeric key will be used as is. This will have no effect other that the code is different in the functions handling keys. User wise there is no difference.
Config file priority
If a config file is added from the env variable CONFIG_FILE then this have the top priority.
After that priority is grouped by type and path.
json files have higher priority than ini files.
First the module looks for a subdirectory called config at the same path where your package.json is located.
If that is not found then it searches the parent directory for at directory called config.
If that is not found then it searches for a subdirectory in the same location as the package.json with the same basename as the executed file.
If that is not found then it searches in the same directory as your package.json
CONFIG_FILE and CONFIG_PATH
The base dirctory is the same directory as the entry file. But ths can be altered by adding the environment variable CONFIG_PATH
By adding environment variable CONFIG_FILE the value here will top the priority list. Note that if the file given doesn't exist then the standard priority list will be used.
If the CONFIG_FILE is a relative path then the default path will be used. If the CONFIG_PATH is an absolute path then this will be used.
Examples
So if we wish to load a development configuration from an entry file called server.js in a directory called serverapp then the following order is processed
node server.js
- /serverapp/config/development.json',
- /config/development.json',
- /serverapp/server/development.json',
- /serverapp/development.json',
- /serverapp/config/development.ini',
- /config/development.ini',
- /serverapp/server/development.ini',
- /serverapp/development.ini',
- /serverapp/config/default.json',
- /config/default.json',
- /serverapp/server/default.json',
- /serverapp/default.json',
- /serverapp/config/default.ini',
- /config/default.ini',
- /serverapp/server/default.ini',
- /serverapp/default.ini'
CONFIG_FILE=test.json node server.js
- /serverapp/test.json
- /serverapp/config/development.json',
- /config/development.json',
- /serverapp/server/development.json',
- /serverapp/development.json',
- /serverapp/config/development.ini',
- /config/development.ini',
- /serverapp/server/development.ini',
- /serverapp/development.ini',
- /serverapp/config/default.json',
- /config/default.json',
- /serverapp/server/default.json',
- /serverapp/default.json',
- /serverapp/config/default.ini',
- /config/default.ini',
- /serverapp/server/default.ini',
- /serverapp/default.ini'
CONFIG_PATH=/server/app node server.js
- /server/app/config/development.json
- /server/config/development.json
- /server/app/server/development.json
- /server/app/development.json
- /server/app/config/development.ini
- /server/config/development.ini
- /server/app/server/development.ini
- /server/app/development.ini
- /server/app/config/default.json
- /server/config/default.json
- /server/app/server/default.json
- /server/app/default.json
- /server/app/config/default.ini
- /server/config/default.ini
- /server/app/server/default.ini
- /server/app/default.ini
CONFIG_PATH=/server/app CONFIG_FILE=test.json node server.js
- /server/app/test.json
- /server/app/config/development.json
- /server/config/development.json
- /server/app/server/development.json
- /server/app/development.json
- /server/app/config/development.ini
- /server/config/development.ini
- /server/app/server/development.ini
- /server/app/development.ini
- /server/app/config/default.json
- /server/config/default.json
- /server/app/server/default.json
- /server/app/default.json
- /server/app/config/default.ini
- /server/config/default.ini
- /server/app/server/default.ini
- /server/app/default.ini
CONFIG_PATH=/server/app CONFIG_FILE=/config/absolute/test.json node server.js
- /config/absolute/test.json
- /server/app/config/development.json
- /server/config/development.json
- /server/app/server/development.json
- /server/app/development.json
- /server/app/config/development.ini
- /server/config/development.ini
- /server/app/server/development.ini
- /server/app/development.ini
- /server/app/config/default.json
- /server/config/default.json
- /server/app/server/default.json
- /server/app/default.json
- /server/app/config/default.ini
- /server/config/default.ini
- /server/app/server/default.ini
- /server/app/default.ini
Chaining
It is rather normal to use if statements like
if(dynConf.has("KEY") && (dynConf.get("KEY2") === "VALUE")) {
// Do something smart
}
This will easily become complex when you need to check multiple keys.
With chaining you can do it like this instead,
if(dynConf.chain().hasKey("KEY").is("KEY2", "VALUE").result()) {
// Do something smart
}
Or if the conditions are spread out in the code you can do it like this.
const chain = dynConf.chain();
// A chunk of code
chain.hasKey("KEY");
// Another chunk of code
chain.is("KEY2", "VALUE")
// Yet another chunk of code before the result should be used
if(chain.result()) {
// Do something smart
}
You can even have multiple chains running in parallel
const chain1 = dynConf.chain();
const chain2 = dynConf.chain();
// A chunk of code
chain1.hasKey("KEY");
chain2.hasNotKey("KEY");
// Another chunk of code
chain1.is("KEY2", "VALUE")
chain2.isNot("KEY2", "VALUE")
// Yet another chunk of code before the result should be used
if(chain1.result()) {
// Do something smart
}
if(chain2.result()) {
// Do something smart
}
Default values
Configuration files can have a fallback configuration file.
...
const dynConf = require('@codedv8/dynamicconfig');
...
const hostname = dynConf.get("hostname", "localhost");
If the hostname isn't found neither in the environment nor in the configuration then the value localhost will be returned.
Throw an error if nothing was found
Getting values from the configuration can have a default value or can throw an error if not found.
...
const dynConf = require('@codedv8/dynamicconfig');
...
const hostname = dynConf.get("hostname", null, true);
If hostname doesn't exist neither in the environment nor in the configuration file then an error will be thrown.