Feature Change: RBAC for Airflow Web UI
All Submissions:
- [YES] Have you added an explanation of what your changes do and why you'd like us to include them?
- [TD] I have updated the documentation accordingly.
- [YES] My code follows the code style of this project.
Current Behavior or Linked Issues
Current changes introduce RBAC for WEB-UI. It will enable the user to create new roles and add privileged based permissions. To enable the RBAC add AIRFLOW__WEBSERVER__RBAC: "True" in the Airflow Common Configs section of the helm-config.yaml file. This overwrites the rbac variable inside the airflow.config.
The changes include an additional code in the create_default_user python script to create the first admin user as it is not created by default. This user can have the same credentials as the one created earlier for Airflow experimental APIs but is handled differently from the API Authentication. The consumer would have the option to create this new user through this script by setting AIRFLOW_RBAC_CREATE_USER flag to "True"
Does this introduce a breaking change?
- NO The user created in this RBAC feature is handled separately from the one that was used before with airflow API authentication, but both can have same values for username and password. So the existing use-case should not be affected by this feature.