From 34d1f2d53ed3f11f4d7961cc34615576ac68880f Mon Sep 17 00:00:00 2001 From: Sergei Petrosian Date: Thu, 4 Apr 2024 17:57:32 +0200 Subject: [PATCH] docs(changelog): version 1.15.2 [citest skip] Update changelog and .README.html for version 1.15.2 Signed-off-by: Sergei Petrosian --- .README.html | 13 +++++++++---- CHANGELOG.md | 16 ++++++++++++++++ 2 files changed, 25 insertions(+), 4 deletions(-) diff --git a/.README.html b/.README.html index 8a1d2ef..1233982 100644 --- a/.README.html +++ b/.README.html @@ -315,12 +315,17 @@ create new profiles with the new provider.
  • network_connections - The connection profiles are configured as network_connections, which is a list of dictionaries that include specific options.
    • -
  • network_allow_restart - Certain configurations require -the role to restart network services. For example, if a wireless +
  • network_allow_restart - It defaults to +false. To load NetworkManager plugins after installation, +NetworkManager requires to be restarted. For example, if a wireless connection is configured and NetworkManager-wifi is not installed, NetworkManager must be restarted prior to the connection being -configured. Setting this to false will prevent the role -from restarting network service.
    • +configured. The restart can result in connectivity loss and therefore +the role does not allow it without explicit consent. The user can +consent to it by setting network_allow_restart to +true. Setting network_allow_restart to +false will prevent the role from restarting +NetworkManager.
  • network_state - The network state settings can be configured in the managed host, and the format and the syntax of the configuration should be consistent with the