NetworkManager may not realize changed connection settings
Closed this issue · 0 comments
jflorian commented
This module does not presently manage the monitor-connection-files
setting so it is dependent upon the defaults of the OS as to whether connection setting changes are realized when the catalog is applied or when the affected connection is bounced.
This module should have a parameter indicating whether any changes are to be realized immediately or deferred. The former behavior is consistent with typical Puppet behavior. Neither former or latter can be considered consistent with backwards behavior because that depends on the OS defaults. Thus this must be considered a breaking change.
It would seem that:
monitor-connection-files
should befalse
(via additional management)nmcli device reapply $DEVICE
should be used instead of (or in addition to) bouncing the service