madison-ookla commented on a change in pull request #13392:
URL: https://github.com/apache/airflow/pull/13392#discussion_r551650467
##########
File path: airflow/upgrade/checker.py
##########
@@ -41,6 +41,15 @@ def check_upgrade(formatter, rules):
return all_rule_statuses
+def list_checks():
+ print()
+ print("Upgrade Checks:")
+ for rule in ALL_RULES:
Review comment:
Just pushed this change, new output (and ordering) looks like this:
```
Upgrade Checks:
- Check for latest versions of apache-airflow and checker [VersionCheckRule]
- Remove airflow.AirflowMacroPlugin class [AirflowMacroPluginRemovedRule]
- Ensure users are not using custom metaclasses in custom operators
[BaseOperatorMetaclassRule]
- Chain between DAG and operator not allowed.
[ChainBetweenDAGAndOperatorNotAllowedRule]
- Connection.conn_type is not nullable [ConnTypeIsNotNullableRule]
- Hooks that run DB functions must inherit from DBApiHook [DbApiRule]
- Fernet is enabled by default [FernetEnabledRule]
- GCP service account key deprecation [GCPServiceAccountKeyRule]
- Unify hostname_callable option in core section [HostnameCallable]
- Changes in import paths of hooks, operators, sensors and others
[ImportChangesRule]
- Legacy UI is deprecated by default [LegacyUIDeprecated]
- Logging configuration has been moved to new section
[LoggingConfigurationRule]
- Removal of Mesos Executor [MesosExecutorRemovedRule]
- No additional argument allowed in BaseOperator.
[NoAdditionalArgsInOperatorsRule]
- Users must set a kubernetes.pod_template_file value [PodTemplateFileRule]
- SendGrid email uses old airflow.contrib module [SendGridEmailerMovedRule]
- Changes in import path of remote task handlers [TaskHandlersMovedRule]
- Jinja Template Variables cannot be undefined [UndefinedJinjaVariablesRule]
- Connection.conn_id is not unique [UniqueConnIdRule]
```
----------------------------------------------------------------
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:
[email protected]
