Same thought as Jarek here. I wasn't too aware of what you meant by deprecated context items, so I went through the link https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html#deprecated-variables and my first qn was, how do I update my DAGs?
We mention this in the docs: *The following variables are deprecated. They are kept for backward compatibility, but you should convert existing code to use other variables instead.* But how? Some direction to fix this and updating the docs for the same would be good. Thanks & Regards, Amogh Desai On Mon, Dec 2, 2024 at 2:40 AM Jarek Potiuk <ja...@potiuk.com> wrote: > Yes. > > As long as we will have a way to signal deprecated values usage (which I > think is possible in 2.11). One "assumption" we want to keep is that when > you move to 2.11 and remove all deprecation warnings, you should be able to > ... just move.. I think this is a nice goal to have, even if it might not > always be 100% achievable - but it should be our "beacon". > > We already have deprecation warnings for context - we are good with that, > so I think we are almost done, but in a few cases, I think we need a bit > more explicit explanation of what users should do when they see > the warnings. Mostly about some old dates (like next_ds). > > There were a few old keys that have no "easy" replacement and so far we > explained what are the deprecated values: > https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html > but it was not really clear how to convert some of those deprecated date > values (I think even for us) - because the logic under the hood changed for > various kinds of time schedules we added in Airflow 2. > > And I think we do not have to provide step-by-step clear and > straightforward answers, but more of a "this worked like this before, those > new things work like this - you need to understand that and figure out > yourself how to best adapt your DAGs". > > Basically I think all deprecation warnings that we have if they cannot be > explained in a single line, should have a link to URL in our docs where we > explain more about "before" and "after" and give the user at least some > guidelines of how they should approach it. > > It should IMHO not only be "easy" to migrate from 2.11 to 3.0 but also easy > to understand how to remove deprecation warnings in 2.11. > > Example questions for that (but I recall there were more): > > * https://github.com/apache/airflow/issues/42806 > * https://github.com/apache/airflow/discussions/40113 > * https://github.com/apache/airflow/issues/14572 > > > J. > > > > > On Sun, Dec 1, 2024 at 9:07 PM Jens Scheffler <j_scheff...@gmx.de.invalid> > wrote: > > > I know, it might be a bit late but still... While cleaning deprecations > > I stumbled over deprecated context entries. > > > > We have documented these entries since 2.0 and still carry them around > > many places in the code. Just wanted to briefly drop this discussion to > > feel the temperature before VOTE. > > > > Does something as argument speaks against removing the (long time) > > deprecated context variables in Airflow 3? > > > > Who does not remember: The deprecated ones are > > > > > https://airflow.apache.org/docs/apache-airflow/stable/templates-ref.html#deprecated-variables > > (or search for AirflowContextDeprecationWarning) > > > > Jens > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: dev-unsubscr...@airflow.apache.org > > For additional commands, e-mail: dev-h...@airflow.apache.org > > > > >
