summaryrefslogtreecommitdiff
path: root/lib/oxidized/source/csv.rb
AgeCommit message (Collapse)Author
2017-01-24GPG supportmbakerbp
2017-01-24Updatembakerbp
2017-01-24Syntax errormbakerbp
2017-01-24Untested GPG workmbakerbp
2016-10-12Interpolate also node variables, not just vars mapSaku Ytti
Fixes #583
2016-09-28interpolate node variable valuesSaku Ytti
Empty value was variably considered "" or nil, now it will always be "" string. Now "nil", "false", "true" strings are converted to their respective types nil, false and true. This also means we cannot have verbatim strings by that name, like if your password was "false", you're shit out of luck. If this is the case, we can add some __false__ hack or consider other similar solutions. Fixes #500 Fixes #534 May break stuff with ""/nil changing now, but as it was not consistent to begin with, I find it acceptable. Users now may need to manually enter nil in some fields to regain old behaviour.
2015-11-13better test framework, more specs and Travis CIElvin Efendi
2015-04-20expand csv pathSaku Ytti
so that ~/foo/bar works
2014-12-13Skip commentsSaku Ytti
closes #64
2014-07-11ignore empty lines in CSV sourceSaku Ytti
Closes #23
2014-05-06require config/vars earlier0.0.56Saku Ytti
- we need config/vars before model - some whitespace changes Bump up gemspec
2014-05-05missing editsAnton Aksola
2014-04-14Use 'asetus' for configuration filesSaku Ytti
Main benefits a) we get support for system wide configs b) we don't use symbols in config file, they're confusing to non-rubyist
2014-02-25Fix crashes on missing configSaku Ytti
We now merge user config with bootstrap config ensuring all configuratio options are set even if not in configuratatin. Allowing us to add new configuration options, without needing for users to touch their existing configuration. All default values are still written to user config when ever CFG.save is called, which means when you change your output/input/source models and configuration is missing, instead of just adding the configuration needed for that particular module, it'll save full config to file. Don't really think that is a bug, but might be something to fix later on with maybe parameter to 'save'. Which would load user config, merge it with 'save' argument level and save user config. But unless someone is bothered by it, I won't do it. This commit fixes #1
2013-04-17Initial commitSaku Ytti
Silly for shit-and-giggles attempt at rancid