Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add a flag to list all Upgrade Check Rules

See original GitHub issue

It would be nice to have a list of all the available uprade-checks rules:

❯ airflow upgrade_check --help
usage: airflow upgrade_check [-h] [-s SAVE] [-i IGNORE] [-c CONFIG]

optional arguments:
  -h, --help            show this help message and exit
  -s SAVE, --save SAVE  Saves the result to the indicated file. The file
                        format is determined by the file extension.
  -i IGNORE, --ignore IGNORE
                        Ignore a rule. Can be used multiple times.
  -c CONFIG, --config CONFIG
                        Path to upgrade check config yaml file.

example (Ideally it should have 2 columns: Check_ID / Class Name and Summary):

❯ airflow upgrade_check --list

- Check for latest versions of apache-airflow and checker
- Remove airflowAirflowMacroPlugin class
- Chain between DAG and operator not allowed
- Connectionconn_id is not unique
- Connectionconn_type is not nullable
- Ensure users are not using custom metaclasses in custom operators
- Fernet is enabled by default
- GCP service account key deprecation
- Unify hostname_callable option in core section
- Changes in import paths of hooks, operators, sensors and others
- Users must delete deprecated configs for KubernetesExecutor
- Legacy UI is deprecated by default
- Logging configuration has been moved to new section
- Removal of Mesos Executor
- No additional argument allowed in BaseOperator
- Users must set a kubernetespod_template_file value
- SendGrid email uses old airflowcontrib module
- Changes in import path of remote task handlers
- Jinja Template Variables cannot be undefined

This allows users to know the progress of their checks and an easy way to ignore a check beforehand (if we list an id / class name too, example PodTemplateFileRule).

Issue Analytics

State:
Created 3 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

kaxilcommented, Dec 30, 2020

Was just adding that too 😃 literally did it few seconds back 😃

Ha, forgive my impatience 😁 ! I’m working on #13349 and #13350 right now, feel free to assign this to me if you wanted!

Awesome, assigned it to you 😄 – thanks. Looking forward to reviewing your PR

0reactions

kaxilcommented, Jan 7, 2021

Closed by https://github.com/apache/airflow/pull/13392

Top Results From Across the Web

How can I update a user flag in rules? - Drupal Answers

My question: how can I fetch the previously applied flag in rules so that I can update the timestamp and re-save it?

Set categories, flags, reminders, or colors - Microsoft Support

Select Home >Follow Up > Add Reminder. In the Custom box, for Flag to, select Follow up or type a description. Check the...

Essential Guide to Feature Flags - Split Software

You can see here that we only include “overnight” in the list of available shipping options if the `FF_OFFER_OVERNIGHT_SHIPPING` flag variable is true....

Feature flags - GitLab Docs

To add users to a user list: On the top bar, select Main menu > Projects and find your project. On the left...

Flag emails in Mail on Mac - Apple Support

To show all messages in the Inbox again, click Inbox in the Mail sidebar or the Favorites bar. You can search for flagged...