After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698069 - cli: provide a command to delete all configured connections
cli: provide a command to delete all configured connections
Status: RESOLVED WONTFIX
Product: NetworkManager
Classification: Platform
Component: nmcli
unspecified
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks: tracker-nmcli
 
 
Reported: 2013-04-15 17:18 UTC by Pavel Simerda
Modified: 2014-01-02 18:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pavel Simerda 2013-04-15 17:18:26 UTC
As a maintainance task, it may be reasonable to delete all connections via CLI. I propose the following syntax as a starting point for further discussion.

nmcli connection delete --all
Comment 1 Dan Winship 2013-04-17 18:50:14 UTC
I understand why you want this command this week, but I can't imagine anyone ever wanting to do this in the real world.

If you have lots of connections, there's probably a reason for most of them (eg, wifi networks you want to remember). And if you don't have lots of connections, then it's easy to delete them one-by-one, and that's better than a delete-all command, because you probably actually want to keep one of them anyway.
Comment 2 Pavel Simerda 2013-04-18 07:40:29 UTC
(In reply to comment #1)
> I understand why you want this command this week, but I can't imagine anyone
> ever wanting to do this in the real world.

This week is like every other week, IMO.

> If you have lots of connections, there's probably a reason for most of them
> (eg, wifi networks you want to remember). And if you don't have lots of
> connections, then it's easy to delete them one-by-one, and that's better than a
> delete-all command, because you probably actually want to keep one of them
> anyway.

The truth is that you can still delete the saved ones with rm * command in the connection directory. But then you need the 'reload' command with nmcli we were also talking about.

This was just an idea, I think we can keep it open for some time in case someone wants to add real use cases, and then, if no relevant feedback comes, we can mark it as WONTFIX.
Comment 3 Dan Winship 2013-04-18 13:03:54 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > I understand why you want this command this week, but I can't imagine anyone
> > ever wanting to do this in the real world.
> 
> This week is like every other week, IMO.

No, this week you're testing a tool for creating connections, in a virtual machine where you don't do any other real work. So you've ended up with lots of connections that you don't actually care about, and no connections that you do care about. This does not normally happen to people.
Comment 4 Dan Winship 2013-05-02 15:59:43 UTC
NM bugzilla reorganization... sorry for the bug spam.
Comment 5 Dan Winship 2014-01-02 18:01:09 UTC
(In reply to comment #2)
> This was just an idea, I think we can keep it open for some time in case
> someone wants to add real use cases, and then, if no relevant feedback comes,
> we can mark it as WONTFIX.