potiuk commented on a change in pull request #11529:
URL: https://github.com/apache/airflow/pull/11529#discussion_r504924221



##########
File path: docs/production-deployment.rst
##########
@@ -387,6 +387,14 @@ The following build arguments (``--build-arg`` in docker 
build command) can be u
 | ``AIRFLOW_BRANCH``                       | ``master``                        
       | the branch from which PIP dependencies   |
 |                                          |                                   
       | are pre-installed initially              |
 
+------------------------------------------+------------------------------------------+------------------------------------------+
+| ``AIRFLOW_CONSTRAINTS_LOCATION``         |                                   
       | If not empty, it will override the       |
+|                                          |                                   
       | source of the constraints with the       |
+|                                          |                                   
       | specified URL or file. Note that the     |
+|                                          |                                   
       | file has to be in docker context so      |
+|                                          |                                   
       | it's best to place such file in          |
+|                                          |                                   
       | one of the folders included in           |
+|                                          |                                   
       | dockerignore                             |

Review comment:
       ```suggestion
   |                                          |                                 
         | docker ignore                            |
   ```




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


Reply via email to