-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Multiple 'up' lines in options hash #18
Comments
My idea for implementing this was to allow up to take an array, within the options hash, like so:
Is this an acceptable solution? |
Looks good to me. |
Just strictly speaking, there is an file(/etc/sysconfig/static-routes) that manages routes - is this in the scope of this module as well? |
@saz I have a topic branch that should have the necessary work to support multiple options in a hash. It passes my unit tests but I don't have the bandwidth to do a lot of acceptance testing on it right now. The branch is at https://github.com/adrienthebo/puppet-network/tree/reimplement_debian_parsing ; would you be willing to test it and see if it works as expected? |
@vjanelle So the situation with static routing configuration is really messy right now. I plan on implementing some sort of static route management, but on Debian it's all but impossible to extract routing and interface configuration. On Redhat it's easier since there are the individual route files as you mention, but the problem I have run into is how to manage the data. If I create a new ticket regarding route configuration with a request for comments on how people want to see it implemented would you be willing to toss you input into that? |
Sure. |
Debian can have multiple arbitrary commands for iface blocks, but the previous behavior was concatenating array entries. This commit adds a separate line for each entry in the value array.
Released in 0.3.0-rc1 |
Debian allows multiple 'up' lines in iface stanza. They will be executed in the order written to the file.
But this isn't possible as there can only be one key in the options hash.
The text was updated successfully, but these errors were encountered: