Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for sections in .conf [JIRA: RIAK-3054] #227

Open
joshuabach opened this issue Nov 25, 2016 · 3 comments
Open

Support for sections in .conf [JIRA: RIAK-3054] #227

joshuabach opened this issue Nov 25, 2016 · 3 comments

Comments

@joshuabach
Copy link

It might be useful to expand the config file parser to support unix-conf-style sections, e.g.:

[foo.bar]
a = 3
b = test

instead of

foo.bar.a = 3
foo.bar.b = test

The semantics could be really simple: Every key $key found in section [$section] is prefixed with $section, resulting in $section.$key.

This would help to avoid redundancy in the .conf files.

@Basho-JIRA Basho-JIRA changed the title Support for sections in .conf Support for sections in .conf [JIRA: RIAK-3054] Nov 25, 2016
@angrycub
Copy link

One of the driving factors for using sysctl-style names as opposed to INI-style groupings allow for any value to be single lined and placed at any point in the file. This, coupled with the last-read wins scheme, allows you to compose configurations very easily by concatenating files from most general to most specific. This form is easily usable from line-based commands like grep.

@joshuabach
Copy link
Author

joshuabach commented Dec 4, 2016

Well, since it could simply be an additional parsing method, this would not be a problem. If (as an admin) I want to be able to use sed, grep and family to manage my configuration files, I can stick to the sysctl syntax, if that is not as important to me, I can use sections. The default generated config might still be syctl-like.

@joshuabach
Copy link
Author

Maybe this can be closed in favor of #207

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants