This repository has been archived by the owner on Oct 17, 2023. It is now read-only.
Simplifies the config.yaml and node configuration #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
makes the nodes config be derived by merging what's in the config.yaml and what is specified in the application.js. the config.yaml node is a map[string]map[string]bool rather then being strictly typed with Type and URI. it's possible to run without a config.yaml entirely.
for example, it's possible to do the following:
with a config.yaml containing:
and run transporter like this:
transporter eval --config test/config.yaml 'Source({name:"localmongo"}).transform({filename:"test/transformers/passthrough_and_log.js"}).save({name:"stdout"})'
as well, you can run with no config by running transporter with:
transporter eval 'Source({name:"localmongo", type: "mongo", uri:"mongodb://localhost/boom", namespace:"boom.foo", tail:true}).transform({filename:"test/transformers/passthrough_and_log.js"}).save({name:"loosefile", type:"file", uri:"file:///tmp/foo"})'
fixes #12