delta/NetworkManager.git/clients/cli/nmcli-completion, branch lr/device-modify

cli/device: add modify command

2016-06-29T18:28:42+00:00

It modifies the applied connection using the Reapply API.

cli: option autocompletion should not match words without trailing '-'

2016-06-28T10:12:39+00:00

This would fix for example:
nmcli e 
(e interpreted as --escape, would allow autocompletion to work... but
when the command is executed an error is reported)

Moreover, we will now have:
nmcli c 
autocompletion work correctly, i.e., c is correctly interpreted  as
"connection" instead of "--colors"

cli: autocompletion: add missing log level and domains

2016-06-27T09:40:39+00:00

Add KEEP level and DHCP, IP, AUDIT, SYSTEMD, VPN_PLUGIN domains.

nmcli: manage autocompletion of "nmcli connection add" when no args are passed

2016-06-23T15:35:08+00:00

This enables back "help" "--help" "-help" in autocompletion.

cli: use --complete-args for connection add completion

2016-06-21T16:40:22+00:00

And make it incredibly slow at the same time.

nmcli: improve connection autocompletion (2/2)

2016-06-21T14:28:48+00:00

Complete the property as we parse the list of properties. This makes it
possible to actually complete an unfinished property.  E.g:

  $ nmcli --complete c modify enp0s25 +ipv6.addr
  +ipv6.addresses +ipv6.addr-gen-mode

nmcli: enable connection autocompletion for 802.1x properties

2016-06-21T14:28:48+00:00

nmcli bash autocompletion leveraged on "nmcli connection edit", "print"
to retrieve the specific properties of a connection. Anyway, the
interactive editor is smart and just prints the used components, so in a
connection where 802.1x is not enabled we had no autocompletion.
Solved adding an "hidden" command "nmcli --complete connection modify"
as suggested in bgo #724860 in order to retrieve ALL the available
properties for use in autocompletion.
Here patch from L.Rintel has been merged to make che --complete option
global to nmcli (first version was local to "connection modify").

https://bugzilla.gnome.org/show_bug.cgi?id=724860
https://bugzilla.redhat.com/show_bug.cgi?id=1301226

nmcli autocompletion cleanups

2016-06-21T14:28:39+00:00

* no need to check HELP_ONLY_AS_FIRST var as when --help option is passed
  _nmcli_compl_OPTIONS will return 0, falling in the general case that
  will trigger end of autocompletion

* clanup local var declaration in _nmcli func:
  - remove dupliated OPTIONS_MANDATORY declaration
  - init HELP_ONLY_AS_FIRST on declaration
  - order vars for common prefix

nmcli-completion: complete filename for VPN import and passwd-file

2016-05-19T10:52:59+00:00

Also hard-code the VPN types strongswan and fortisslvpn.

https://bugzilla.redhat.com/show_bug.cgi?id=1337300

cli: don't allow multiple arguments to device-reapply

2016-05-03T09:52:57+00:00

Just like `nmcli device connect` only allows one argument, don't allow
multiple device arguments for reapply.

Allowing multiple device names makes it more complicated to add
additional options to the command. For example, it would be useful
to have a

    nmcli device reapply eth0 connection id other-connection

but when allowing multiple device names, it gets more complicated in
documentation, command line parsing and bash completion.

Note that the user can achieve a very similar outcome by using the
shell:

    for DEV in eth0 eth1 eth2; do
        nmcli device reapply $DEV &
    done
    wait

argubaly, this doesn't report the exit status properly. To properly
handle that would require more effort. Also, it is somewhat less
efficient, but well.

This is an API change, however it is very new API that probably nobody
is using much. Also, the documentation (man nmcli) didn't mention the
possibility to pass multiple device names.