You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@airflow.apache.org by "Victor Villas Bôas Chaves (JIRA)" <ji...@apache.org> on 2018/12/27 04:19:00 UTC

[jira] [Created] (AIRFLOW-3572) Docs implies that providing remote_log_conn_id is mandatory

Victor Villas Bôas Chaves created AIRFLOW-3572:
--------------------------------------------------

             Summary: Docs implies that providing remote_log_conn_id is mandatory
                 Key: AIRFLOW-3572
                 URL: https://issues.apache.org/jira/browse/AIRFLOW-3572
             Project: Apache Airflow
          Issue Type: Improvement
          Components: Documentation
    Affects Versions: 1.10.1
            Reporter: Victor Villas Bôas Chaves


The docs on setting up remote logging with S3 currently states:

> To enable this feature, airflow.cfg must be configured as in this example:

... example ...

> In the above example, Airflow will try to use {{S3Hook('MyS3Conn')}}.

When in fact you can just leave `remote_log_conn_id =` (or nothing, because that's the default) if you have your credentials set in the process environment, because Airflow will fallback to boto3 config auto-detection.


This behavior is by purpose as the comment hints [here|https://github.com/apache/incubator-airflow/blob/master/airflow/contrib/hooks/aws_hook.py#L155-L158] so it should be documented.



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