-
-
Notifications
You must be signed in to change notification settings - Fork 199
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
Feature Request - Order Matters #97
Comments
Could also easily implement backwards compatibility - detect if the current object is a hash, push it on to an array and save |
Same problem for me. |
I would also vote for this, especially because of the need to sometimes precede or disable one of the default facilities. E.g. I want to be able to send all |
Like in most things, order matters within the rsyslog.conf - it would be swell if instead of a hash for the rsyslog.default_facility_logs and rsyslog.additional_directives it was an array of hashes, so that way line order could be easily specified.
Within each array, a simple sort would/should be applied to ensure random array storage doesn't cause the file to be needlessly regenerated. So the template would end up looking like
This would grant people to slice, push, pop, etc entries the way they wanted.
The defaults could still be implemented as hash, just the first hash in the array
The text was updated successfully, but these errors were encountered: