potiuk opened a new issue #11144: URL: https://github.com/apache/airflow/issues/11144
This issue is part of #8765 ## Rule Create `UndefinedJinjaVariablesRule` which corresponds to > Prior to Airflow 2.0 Jinja Templates would permit the use of undefined variables. They would render as an empty string, with no indication to the user an undefined variable was used. With this release, any template rendering involving undefined variables will fail the task, as well as displaying an error in the UI when rendering. entry in UPDATING.md. Introduced in #11016 This rule should check if any of the jinja templates use undefined variables. This might not be always possible, as this might involve the dynamic generation of some context variables, but likely we can at least print some warning or "double-check this" statements. ## How to guide To implement a new rule, create a class that inherits from `airflow.upgrade.rules.base_rule.BaseRule`. It will be auto-registered and used by `airflow upgrade-check` command. The custom rule class has to have `title`, `description` properties and should implement `check` method which returns a list of error messages in case of incompatibility. For example: https://github.com/apache/airflow/blob/ea36166961ca35fc51ddc262ec245590c3e236fb/airflow/upgrade/rules/conn_type_is_not_nullable.py#L25-L42 **Remember** to open the PR against `v1-10-test` branch. ---------------------------------------------------------------- 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: us...@infra.apache.org
