You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2019/12/19 19:07:00 UTC

[jira] [Commented] (AIRFLOW-6310) Group CLI commands in subcommands

    [ https://issues.apache.org/jira/browse/AIRFLOW-6310?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17000307#comment-17000307 ] 

ASF GitHub Bot commented on AIRFLOW-6310:
-----------------------------------------

mik-laj commented on pull request #6858: [AIRFLOW-6310] Group CLI commands in subcommands
URL: https://github.com/apache/airflow/pull/6858
 
 
   
   
   This is not finished PR. It is necessary to update the tests, but I decided to share it to get an opinion before investing more time. I would like to suggest that you group several commands to help users find the right command.
   
   | Old command               | New command                        |
   |---------------------------|------------------------------------|
   | airflow kerberos          | airflow run kerberos               |
   | airflow webserver         | airflow run webserver              |
   | airflow scheduler         | airflow run scheduler              |
   | airflow worker            | airflow run worker                 |
   | airflow flower            | airflow run flower                 |
   | airflow config            | airflow config show                |
   | airflow rotate_fernet_key | airflow config rotate_fernet_key   |
   
   After execution we will have only two clean commands in airflow (without subcomands):
   * sync_perm
   * version
   
   Make sure you have checked _all_ steps below.
   
   ### Jira
   
   - [ ] My PR addresses the following [Airflow Jira](https://issues.apache.org/jira/browse/AIRFLOW/) issues and references them in the PR title. For example, "\[AIRFLOW-XXX\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-XXX
     - In case you are fixing a typo in the documentation you can prepend your commit with \[AIRFLOW-XXX\], code changes always need a Jira issue.
     - In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal ([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals)).
     - In case you are adding a dependency, check if the license complies with the [ASF 3rd Party License Policy](https://www.apache.org/legal/resolved.html#category-x).
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   
   ### Tests
   
   - [ ] My PR adds the following unit tests __OR__ does not need testing for this extremely good reason:
   
   ### Commits
   
   - [ ] My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)":
     1. Subject is separated from body by a blank line
     1. Subject is limited to 50 characters (not including Jira issue reference)
     1. Subject does not end with a period
     1. Subject uses the imperative mood ("add", not "adding")
     1. Body wraps at 72 characters
     1. Body explains "what" and "why", not "how"
   
   ### Documentation
   
   - [ ] In case of new functionality, my PR adds documentation that describes how to use it.
     - All the public functions and the classes in the PR contain docstrings that explain what it does
     - If you implement backwards incompatible changes, please leave a note in the [Updating.md](https://github.com/apache/airflow/blob/master/UPDATING.md) so we can assign it to a appropriate release
   
 
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


> Group CLI commands in subcommands
> ---------------------------------
>
>                 Key: AIRFLOW-6310
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-6310
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: cli
>    Affects Versions: 1.10.6
>            Reporter: Kamil Bregula
>            Priority: Major
>
> Some commands have been grouped to improve UX of CLI. New commands are available according to the following 
> table:
> | Old command               | New command                        |
> |---------------------------|------------------------------------|
> | airflow kerberos          | airflow run kerberos               |
> | airflow webserver         | airflow run webserver              |
> | airflow scheduler         | airflow run scheduler              |
> | airflow worker            | airflow run worker                 |
> | airflow flower            | airflow run flower                 |
> | airflow config            | airflow config show                |
> | airflow rotate_fernet_key | airflow config rotate_fernet_key   |



--
This message was sent by Atlassian Jira
(v8.3.4#803005)