-
Notifications
You must be signed in to change notification settings - Fork 14.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deprecated kerberos auth removed #41693
Conversation
…rflow.auth.managers.fab.api.auth.backend.kerberos_aut removed
…rflow.auth.managers.fab.api.auth.backend.kerberos_aut removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Breaking change must have news fragment to notify users what was removed and how to mitigate. In this case just alerting about module remove and how to set it up with fab provider
I have already added the news fragment. Am I missing anything? |
@eladkal ? |
Sorry, need to be another bad guy here. We said for Airflow 3 dev rules we must separate PRs for providers and stuff for the core. Assume we need to split this here as well. (1) for provider update and (2) for removing/breaking change in core. (whereas I assume we don't plan to back-port to 2.10 so technically could be one PR?) |
@eladkal |
Yep I think it is needed. But we might actually want only core changes, breaking change in providers will result in creating major versions which we might not want yet. I'll let @eladkal confirm |
@dirrao Could you please update this PR (or create another one) to include only changes from core? |
Actually I think your changes are fine. It seems inevitable to force Airflow 3 to use the latest FAB version provider. See comment here. If that is the case your changes are not breaking for providers. You back ported |
Yes, my changes are backward compatible. They will simply start using the FAB provider module instead of the deprecated core auth module. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The commit message says removed deprecation but this PR also adds more functionality to the provider. Is the commit message right?
The only code added to the provider is code moved from core to provider. There is no new functionality. I think the message is fair |
Yes. No new functionality added. |
ok then I will modify the provider change log |
* deprecatd kerberos auth airflow.api.auth.backend.kerberos_auth and airflow.auth.managers.fab.api.auth.backend.kerberos_aut removed * news fragment added * deprecatd kerberos auth airflow.api.auth.backend.kerberos_auth and airflow.auth.managers.fab.api.auth.backend.kerberos_aut removed
* deprecatd kerberos auth airflow.api.auth.backend.kerberos_auth and airflow.auth.managers.fab.api.auth.backend.kerberos_aut removed * news fragment added * deprecatd kerberos auth airflow.api.auth.backend.kerberos_auth and airflow.auth.managers.fab.api.auth.backend.kerberos_aut removed
The following deprecated kerberos auth removed