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

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

xnuinside opened a new pull request #4174: [AIRFLOW-571] Airflow CLI: add 
gunicorn_config param and refactor webserver cli function
URL: https://github.com/apache/incubator-airflow/pull/4174
 
 
   … possible to test it
   
   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-571\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-571
     - 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:
   
   I added gunicorn_config (-gc) param for get possible send all params what 
available in gunicorn server without adding support of them as separate args in 
Airflow. I also refactored webserver function with saving full backward 
compatibility. It's necessary to get possible to add tests. 
   
   Please, look at PR and if technical there are no issues, I will add also 
changes to doc. 
   
   ### 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 `flake8`
   

----------------------------------------------------------------
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:
[email protected]


> allow gunicorn config to be passed to airflow webserver
> -------------------------------------------------------
>
>                 Key: AIRFLOW-571
>                 URL: https://issues.apache.org/jira/browse/AIRFLOW-571
>             Project: Apache Airflow
>          Issue Type: Improvement
>          Components: webserver
>            Reporter: Dennis O'Brien
>            Assignee: Iuliia Volkova
>            Priority: Major
>
> I have run into an issue when running airflow webserver behind a load 
> balancer where redirects result in https requests forwarded to http.  I ran 
> into a similar issue with Caravel which also uses gunicorn.  
> https://github.com/airbnb/caravel/issues/978  From that issue:
> {quote}
> When gunicorn is run on a different machine from the load balancer (nginx or 
> ELB), it needs to be told explicitly to trust the X-Forwarded-* headers sent. 
> gunicorn takes an option --forwarded-allow-ips which can either be a comma 
> separated list of ip addresses, or "*" to trust all.
> {quote}
> I don't see a simple way to inject custom arguments to the gunicorn call in 
> `webserver()`.  Rather than making a special case to set 
> --forwarded-allow-ips, it would be nice if the caller of `airflow webserver` 
> could pass an additional gunicorn config file.
> The call to gunicorn is already including a -c and I'm not sure gunicorn will 
> take multiple configs, so maybe we have to parse the config and include each 
> name=value on the gunicorn command line.  Any suggestions on how best to 
> allow this?



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

Reply via email to