jason810496 commented on PR #56150: URL: https://github.com/apache/airflow/pull/56150#issuecomment-3427509923
> Is there a standard way for marking a config as deprecated? I have found what to do with configs that will change in the future (moved or renamed) but I'm not sure about the ones that will be removed. Sorry, I oversight this message. This is the place where we deprecate the config section-option pair, but it _seems_ only work for `(new section, new option) -> (old section, old option, since_version)` case. https://github.com/apache/airflow/blob/f3ad20aad803196b6fc1c73c1a38560deaf31aee/airflow-core/src/airflow/configuration.py#L345-L349 I'm not sure how should we deal with **removing** the config pair as well. @potiuk may we ask for what is the correct and standard way to **removing** the config pair? -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
