Trivial Airflow 2.0 will error when operators are instantiated with unused keyword arguments, but for now unused arguments just raise a warning. My team has passed unused arguments to operators and not noticed the warning a few times, and it would be useful to be able to opt in to airflow 2.0 validation early. I propose adding a configuration flag that causes tasks to error on unused arguments.
- links to