Address deprecations, make DeprecationWarning and RemovedInAirflow3Warning raise error #4951
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When running
ov just catalog/test
recently, I noticed that we had a few new deprecation errors:This PR:
RemovedInAirflow3Warning
by adding an enforcedschedule
to all the DAGs which are referenced in the warningDeprecationWarning
, since that's an upstream issue within Airflow's providersDeprecationWarning
andRemovedInAirflow3Warning
to raise an error when they occurI believe this was the result of #4897, but by default we don't have a whole lot of visibility into deprecation warnings (since they don't show up as an error on CI). This PR changes the warnings so we have to address them as part of any version upgrades we're doing for the catalog. Because of the Airflow constraints file, we shouldn't run into out-of-band deprecation warnings on unrelated PRs; most of the versions of our packages & dependencies are pinned and won't change unless we're updating the version of Airflow itself.
Testing Instructions
ov just catalog/test
RemovedInAirflow3Warning
now becomes a test failure rather than appearing in the warnings summary.Checklist
Update index.md
).main
) or a parent feature branch.ov just catalog/generate-docs
for catalogPRs) or the media properties generator (
ov just catalog/generate-docs media-props
for the catalog or
ov just api/generate-docs
for the API) where applicable.Developer Certificate of Origin
Developer Certificate of Origin