ianbuss opened a new pull request #22051:
URL: https://github.com/apache/airflow/pull/22051


   A new configuration parameter "CORE_IGNOREFILE_SYNTAX" is added to
   allow patterns in .airflowignore files to be interpreted as either
   regular expressions (the default) or glob expressions as found in
   .gitignore files. This allows users to use patterns they will be
   familiar with from tools such as git, helm and docker.
   
   Glob expressions support wildcard matches ("*", "?") within a directory
   as well as character classes ("[0-9]"). In addition, zero or more
   directories can be matched using "**". Patterns can be negated by
   prefixing a "!" at the beginning of the pattern.
   
   The "fnmatch" library in core Python does not produce patterns that are
   fully compliant with the kind of patterns that users will be used to
   from gitignore or dockerignore files, so the globs are parsed using
   the gitignore-parser package from PyPI.
   
   To aid with debugging ignorefile patterns a more helpful error
   message is emitted in the logs for invalid patterns, which are
   now skipped rather than causing a hard-to-read scheduler stack trace.
   
   ---
   **^ Add meaningful description above**
   
   Read the **[Pull Request 
Guidelines](https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst#pull-request-guidelines)**
 for more information.
   In case of fundamental code change, Airflow Improvement Proposal 
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvements+Proposals))
 is needed.
   In case of a new dependency, check compliance with the [ASF 3rd Party 
License Policy](https://www.apache.org/legal/resolved.html#category-x).
   In case of backwards incompatible changes please leave a note in 
[UPDATING.md](https://github.com/apache/airflow/blob/main/UPDATING.md).
   


-- 
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]


Reply via email to