Thomas Haller 68bd018a88 cli: prefer matching connections by "uuid" instead of "id" ... Scripts should refer to connections by UUID. That means, whenever a UUID matches, that is really what the user wants. The specifier "uuid" must have precedence over "id" (and all others). That means, we must search all connections. For example: $ UUIDS=($(nmcli -g TYPE,UUID connection show | sed -n 's/802-11-wireless://p')) $ nmcli -f connection.id,connection.uuid connection show "${UUIDS[@]}" in this case we must preferrably match by UUID, regardless of whether a "connection.id" exists. Note that if you have: $ nmcli connection show | grep fdf7b2d2-2858-3938-9b14-7f1b514a9a00 b fdf7b2d2-2858-3938-9b14-7f1b514a9a00 ethernet -- fdf7b2d2-2858-3938-9b14-7f1b514a9a00 ab9f3891-3420-335e-89da-f14c1b94c540 ethernet -- then certain commands will still select all matching connections: $ nmcli -f connection.id,connection.uuid --mode multiline connection show fdf7b2d2-2858-3938-9b14-7f1b514a9a00 connection.id: fdf7b2d2-2858-3938-9b14-7f1b514a9a00 connection.uuid: ab9f3891-3420-335e-89da-f14c1b94c540 connection.id: b connection.uuid: fdf7b2d2-2858-3938-9b14-7f1b514a9a00 This only makes a difference for commands that must pick only one profile: $ nmcli connection modify fdf7b2d2-2858-3938-9b14-7f1b514a9a00 con-name new-name		2019-04-15 20:50:50 +02:00
..
cli	cli: prefer matching connections by "uuid" instead of "id"	2019-04-15 20:50:50 +02:00
common	nmcli: fix an error message when the tc qdisc kind is missing	2019-04-12 17:30:15 +02:00
tests	clients: disable asan leak detection in client tests	2019-04-12 11:19:58 +02:00
tui	clients: only ask secrets for settings that require them	2019-04-02 11:20:28 +02:00
meson.build	build: meson: Add trailing commas	2018-12-20 13:50:34 +01:00
nm-online.c	nm-online: sort options in man page and program help	2018-11-05 09:32:20 +01:00