Hello,
On 07/02/2020 15:38, Pär Stolpe via PacketFence-users wrote:
yes we have considered templates but:
With templates the configuration file becomes static, with Auegas we may modify
only the changes we need to be controlled and may use the gui for everything
else.
I understand but you should be able to have same behavior with module
different than Augeas. With Ansible, there is a ini module that allow
you to edit only a specific key/value in a conf file.
Templates do not consider upstream changes, with Auegas it's easier to upgrade
if new features demands changes in default config files.
It depends how you generate template. If you're able to generate
template from a YAML dictionnary in your inventory, you can keep in sync
with upstream as long as you update your inventory.
Preferably if there is a way to set the key and values in the config file as
something like below and thus avoid the / in the key-value [ key ] ?
[switch-name]
ipv4=
ipv6=
mac=
I don't think so, you can create a feature request on your bug tracker:
https://github.com/inverse-inc/packetfence/issues/new?assignees=&labels=Type%3A+Feature+%2F+Enhancement&template=feature_request.md&title=
--
Nicolas Quiniou-Briand
[email protected] :: +1.514.447.4918 *140 :: https://inverse.ca
Inverse inc. :: Leaders behind SOGo (https://sogo.nu), PacketFence
(https://packetfence.org) and Fingerbank (http://fingerbank.org)
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
