airflow-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AIRFLOW-3011) CLI command to output actual airflow.cfg
Date Sat, 08 Sep 2018 22:14:00 GMT

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

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

dispower opened a new pull request #3867: [AIRFLOW-3011][CLI] Add cmd function printing config
URL: https://github.com/apache/incubator-airflow/pull/3867
 
 
   …efined
   
   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-3011\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-3011
     - 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.
   
   ### Description
   
   - [ ] Here are some details about my PR, including screenshots of any UI changes:
   Example of usage:
   Bash command: airflow config` 
   Example of printed config is described on a screenshoot below.
   ![image](https://user-images.githubusercontent.com/13046970/45258969-2547de00-b3cb-11e8-856e-3f3fa033f59a.png)
   
   Output of the same command could be redirected into file and then used for further operations.
   ![image](https://user-images.githubusercontent.com/13046970/45258981-63450200-b3cb-11e8-9228-c700d041e9f5.png)
   
   ### 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.
     - When adding new operators/hooks/sensors, the autoclass documentation generation needs
to be added.
   
   ### Code Quality
   
   - [ ] Passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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


> CLI command to output actual airflow.cfg
> ----------------------------------------
>
>                 Key: AIRFLOW-3011
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3011
>             Project: Apache Airflow
>          Issue Type: New Feature
>          Components: cli
>    Affects Versions: 1.10.0
>            Reporter: Victor
>            Assignee: Valerii Zhuk
>            Priority: Major
>
> The only way to see the actual airflow configuration (including overriden informations
with environment variables) is through web ui.
> For security reason, this is often disabled.
> A CLI command to do the same thing would:
>  * give admins a way to see it
>  * give operators a way to manipulate the configuration (storing it, etc)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message