summaryrefslogtreecommitdiff
path: root/introspection
diff options
context:
space:
mode:
authorThomas Haller <thaller@redhat.com>2019-07-31 12:13:27 +0200
committerThomas Haller <thaller@redhat.com>2019-07-31 13:22:33 +0200
commit2733a41bfd8c88de4aa0959de43c40e89555f382 (patch)
tree37e4d9838cde6efffe018bc41dbb40a3685c54f4 /introspection
parent20f735972fc2006d28dc6372332d39ca2af322db (diff)
downloadNetworkManager-2733a41bfd8c88de4aa0959de43c40e89555f382.tar.gz
introspection/doc: better document flags argument of Update2() D-Bus command
(cherry picked from commit f453eeb588390621b34d93d922ff2592aa0962a5)
Diffstat (limited to 'introspection')
-rw-r--r--introspection/org.freedesktop.NetworkManager.Settings.Connection.xml9
1 files changed, 8 insertions, 1 deletions
diff --git a/introspection/org.freedesktop.NetworkManager.Settings.Connection.xml b/introspection/org.freedesktop.NetworkManager.Settings.Connection.xml
index 2cbb6c2ebc..6211274fd9 100644
--- a/introspection/org.freedesktop.NetworkManager.Settings.Connection.xml
+++ b/introspection/org.freedesktop.NetworkManager.Settings.Connection.xml
@@ -111,7 +111,8 @@
"0x4" (in-memory-detached),
"0x8" (in-memory-only),
"0x10" (volatile),
- "0x20" (block-autoconnect).
+ "0x20" (block-autoconnect),
+ "0x40" (no-reapply).
Unknown flags cause the call to fail.
@args: optional arguments dictionary, for extensibility. Currently no
arguments are accepted. Specifying unknown keys causes the call
@@ -124,6 +125,12 @@
the change is only made in memory (without touching an eventual
profile on disk). If neither 0x1 nor 0x2 is set, the change is made
in memory only, if the connection is already in memory only.
+ The flags 0x4 (in-memory-detached) and 0x8 (in-memory-only) are like
+ "in-memory", but behave slightly different when migrating the profile
+ from disk to in-memory.
+ The flag 0x20 (block-autoconnect) blocks auto-connect on the updated
+ profile, and 0x40 (no-reapply) prevents "connection.zone" and "connection.metered"
+ properties to take effect on currently active devices.
Secrets may be part of the update request, and will be either stored in persistent
storage or sent to a Secret Agent for storage, depending on the flags
associated with each secret.