[
https://issues.apache.org/jira/browse/AIRFLOW-3179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16794556#comment-16794556
]
Ash Berlin-Taylor commented on AIRFLOW-3179:
--------------------------------------------
I want to rename airflow_travis.cfg, specify this one config file via
{{AIRFLOW_CONFIG}}, remove default_tests.cfg file and remove the
`configuration.load_test_config()` function entirely.
And have the config file set internally as part of the test runner/suite, so
that running tests locally don't fail due to unexpectedly using the wrong
config. airflow_travis.cfg (as it is now called) is not travis config, but unit
test config!
In doing this change we would also remove the code that writes
~/airflow/unittest.cfg which has always been a low-level annoyance of mine.
> Remove airflow_travis.cfg
> -------------------------
>
> Key: AIRFLOW-3179
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3179
> Project: Apache Airflow
> Issue Type: Task
> Components: configuration
> Reporter: Ash Berlin-Taylor
> Priority: Minor
>
> We appear to have a different config for running tests on Travis to running
> tests locally/in docker.
> This means that for me locally the tests/configuration.py tests fail.
> We should remove this extra config file *or* remove the default_test.cfg file
> and only make use of this one config file. Either way having two is bad.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
