RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1290634 - RFE firewalld should support short options
Summary: RFE firewalld should support short options
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.1
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Thomas Woerner
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-11 00:54 UTC by wibrown@redhat.com
Modified: 2017-06-23 16:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-06-23 16:56:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description wibrown@redhat.com 2015-12-11 00:54:38 UTC
Description of problem:
One of the complaints about firewalld is the long winded and verbose syntax on the cli. Every option is long, prefixed with --, and hard to remember.

There are other commands, such as nmcli that do not have this issue, and like certain networking vendors products, allows short forms of commands.

An example of firewalld with this would be:

firewalld-cmd z int sad tftp p

This would be equivalent to

firewalld-cmd --zone=internal --service-add=tftp --permanent

This will help lower the barrier to entry to sys admins who appreciate terse compact cli notation for tasks. Improving the efficiency of what an admin will do will increase acceptance and adoption of firewalld.

Comment 2 Eric Garver 2017-06-23 16:56:28 UTC
(In reply to wibrown from comment #0)
> Description of problem:
> One of the complaints about firewalld is the long winded and verbose syntax
> on the cli. Every option is long, prefixed with --, and hard to remember.

I would argue that short options are harder to remember than long options. Eventually you have collisions and end up with short options like grep's "-v" for invert.

> There are other commands, such as nmcli that do not have this issue, and
> like certain networking vendors products, allows short forms of commands.
> 
> An example of firewalld with this would be:
> 
> firewalld-cmd z int sad tftp p
> 
> This would be equivalent to
> 
> firewalld-cmd --zone=internal --service-add=tftp --permanent
> 
> This will help lower the barrier to entry to sys admins who appreciate terse
> compact cli notation for tasks. Improving the efficiency of what an admin
> will do will increase acceptance and adoption of firewalld.

It's also error prone. Fat finger mistakes are pretty unforgiving for a firewall.

If you find a compelling reason firewalld should support short options, please re-open this bug.


Note You need to log in before you can comment on or make changes to this bug.