We are using your role to configure our servers. However, we have an issue for configuring Proxmox: it only loads the network configuration from /etc/network/interfaces (on Debian) and doesn't care about interfaces.d folder.
We would like to be able to store the config in a single file, using an option, for this special use case.
I'd like you opinion before working on a PR because the role is a bit complex:
My first idea would be to use *assemble to gather all interfaces.d files in interfaces (But I'm not sure if composing content from interface name ordering is OK). We just need to put loopback config in a separate file and assemble the folder (light changes). All the mechanics are left untouched because they rely on still existing separate files but not included
Another idea is to completely disable single files in this case. I'm not sure though why a bounce is triggered if the running config does not match the target config AND also when the configuration file is changed (I think that not having the bounce on the later one is ok because if the config file is changed it means that the bounce will happen anyway.
Another option, regardless of keeping or not separate files, could be to use a template with includes if the declaration order is important
jbe-dw
commented
1 year ago
Hello,
We are using your role to configure our servers. However, we have an issue for configuring Proxmox: it only loads the network configuration from /etc/network/interfaces (on Debian) and doesn't care about interfaces.d folder.
We would like to be able to store the config in a single file, using an option, for this special use case.
I'd like you opinion before working on a PR because the role is a bit complex:
Regards J