source-configs

 

A Node.js module that allows you to declaratively define a hierarchy of configuration values for your app from command line arguments, environment variables, or defaults based on a JSON schema you define within your app.

This module was built and is maintained by the Roosevelt web framework team, but it can be used independently of Roosevelt as well.

Usage

First declare source-configs as a dependency in your app.

Then create a config schema JSON object to tell source-configs what config values to listen for.

Here's a simple example declaring that our application will use a WebSocket with a configurable host, port, and protocol:

``javascript
const sourceConfigs = require('source-configs')
const schema = require({
websocket: {
host: {
description: 'WebSocket host URL',
default: 'localhost',
commandLineArg: ['--websocket-host-url', '--ws-host', '-h'],
envVar: ['WEBSOCKET_HOST_URL', 'WS_HOST']
},
port: {
description: 'WebSocket port',
default: 8081,
commandLineArg: ['--ws-port', '-p'],
envVar: 'WS_PORT'
},
protocol: {
description: 'Which WebSocket protocol',
values: ['ws', 'wss'],
commandLineArg: '--ws-protocol',
envVar: 'WS_PROTOCOL'
},
url: 'user-defined function'
}
})

// define the user-defined function above
schema.websocket.url = (config) => config.protocol + '://' + config.host + ':' + config.port

// run source-configs against the schema
const config = sourceConfigs(schema)

// access one of the configs
console.log(config.websocket.port)
`

$3

Schemas support the following metadata for each configurable property in order to create constraints if desired or add additional functionality:

- description [String]: Describe what this config will be used for.
- default [any]: Set a default value for this config. If not set, the default will be set to the config's name.
- values [Array]: Enumerated list of values that are valid. If not set, any value will be valid.
- commandLineArg [String|Array]: Command line argument(s) to listen for that will set this config. If not set, source-configs will not listen for command line arguments to set the value for this config.
- envVar [String|Array]: Environment variable(s) to listen for that will set this config. If not set, source-configs will not listen for an environment variable to set the value for this config.
- secret [Boolean]: Whether or not this value is sensitive information, like a password.

$3

Additionally, a schema can be a function which has the parent config passed to it as the first argument. To do this create a key/value pair within the schema object:

- If the schema is stored in a .js file, set the key as the desired function name and the value as the function.
- If using a .json file to store the schema, set the key as the desired function name and the value as 'user-defined function'. Once the .json file is required in, override the key's value with the desired function.

$3

In addition to the above instantiation method, source-configs also accepts an optional configuration object that can be passed to the constructor as a second object like so:

`javascript
const sourceConfigs = require('source-configs')
const schema = require('./your-schema-js-file.json')

const config = sourceConfigs(schema, {
logging: true,
sources: [
'command line',
'environment variable',
{ custom: 'object' }
]
})
`

#### Available parameters

- logging: Whether or not source-configs will log to console.

- Default: [Boolean] true.

- sources: An array of sources that can be a mix of built-in sources and custom source objects in order of priority.

- Default [Array]:

`javascript
'command line',
'environment variable',
`

- Note: built-in sources can also be referenced in multiple ways:

- Command line: command line or commandLineArg.
- Environment variable: environment variable or envVar

- You can also add custom sources this way by supplying an object to this array:

`javascript
'command line',
'environment variable',
{ custom: 'object' }
`

- transform: A function that can be used to mutate your config after it has been parsed and sourced but before it gets returned by source-configs.

- Example:

`javascript
const sourceConfigs = require('source-configs')
const schema = require('./your-schema-js-file.json')

const config = sourceConfigs(schema, {
transform: (config, commandLineArgs) => {
// check for a cli flag that wouldn't normally translate into a config
if (commandLineArgs.switchPort === true) {
config.websocket.port = 43711
}

// return the config when done
return config
}
})

// access that config configs
console.log(config.websocket.port)
//=> 43711
`

- API:

- transform(config, commandLineArgs): Config transform method.
- config: The config after being parsed by source-configs.
- commandLineArgs: CLI flags as parsed by yargs-parser.

$3

In addition to its constructor, source-configs exposes the following properties:

- configs [Object]: The resulting configs after running source-config's constructor.
- commandLineArgs [Array]: All command line arguments passed to your application, including those not listened for by your schema. Powered by yargs-parser.
- yargsParser [Function]: The instance of yargs-parser that source-configs used to compile all command line arguments passed to your application.
- printHelp [Function]: A function which will generate a help menu describing the command line arguments defined in the schema. Useful for if you want to define a -h or --help command line argument to print all available supported command line arguments. Just print console.log(config.printHelp()) to print that information to your users.
- safelyPrintSchema [Function]: A function which will print the fully post-processed schema to the console, but obscure any data that is marked as secret`.