zach-overflow opened a new issue, #53716: URL: https://github.com/apache/airflow/issues/53716
### Description The proposal for this issue: we should add deprecation warnings for the `airflow.security.permissions` module so the deprecation status is unambiguous to end users of Airflow 3.x who may currently rely on that module. These warnings should indicate that the newer standards to migrate to are as follows: * `airflow.security.permissions.ACTION_CAN_*` constants -> [`ResourceMethod`](https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/api_fastapi/auth/managers/base_auth_manager.py#L66) (and [`ExtendedResourceMethod`](https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/api_fastapi/auth/managers/base_auth_manager.py#L68)) * `airflow.security.permissions.RESOURCE_*` constants -> relevant definitions under [`resource_details.py`](https://github.com/apache/airflow/blob/3.0.3/airflow-core/src/airflow/api_fastapi/auth/managers/models/resource_details.py) ### Use case/motivation As part of the Auth Manager interface rollout, the older `airflow.security.permissions` module has been superseded by the newer `ResourceMethod` and `airflow.api_fastapi.auth.managers.models.resource_details` standards. As such, the usage of `airflow.security.permissions` should probably be phased out over the longterm. Obviously, the full decommissioning of that module will require broader coordination, and future updates within the FAB auth manager, along with ample warnings and communication to users who may still rely on the older permissions module. The motivation for this issue is to start surfacing those warnings now. ### Related issues This came up in the very helpful thread here: https://github.com/apache/airflow/issues/51971 ### Are you willing to submit a PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
