juditnovak commented on PR #59389: URL: https://github.com/apache/airflow/pull/59389#issuecomment-3953139073
I referred to this proposal in comment https://github.com/apache/airflow/pull/59390#discussion_r2616410567 (I marked it resolved after the approval I recall). In PR https://github.com/apache/airflow/pull/59390, I added to the System Test documentation a new section: [Custom configuration file](https://github.com/apache/airflow/blob/main/contributing-docs/testing/system_tests.rst#custom-configuration-file), which currently presents the single option of a "hard-coded" way to load configuration dedicated for System Tests. This proposal is to offer a more elegant and handy solution for this purpose. Use case: ability to load a custom, system-test-specific Airflow configuration file from a specific location when invoking the execution of the System Tests. (Existing example: in the System Test pipelines for project https://github.com/juditnovak/airflow-provider-nomad I'm currently using the ['hard-coded' solution](https://github.com/juditnovak/airflow-provider-nomad/blob/main/tests/system/nomad/conftest.py#L303)...) Assuming that other devs may have also come across the issue, it may be convenient to have the option enabled by the Airflow System Tests plugin itself. (Also, an advantage of this solution is that it is different from any existing options for loading Airflow configuration files that apply to production Airflow instances, ensuring to avoid "potential mistakes".) Of course, if this proposal is to be taken onboard, I'm adding to this very same PR the corresponding docs changes as well, targeting the section mentioned above. -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
