You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/12/04 19:41:28 UTC

[GitHub] [airflow] brunoffaustino edited a comment on issue #8609: DAG's parameter access_control is not refreshing in the UI

brunoffaustino edited a comment on issue #8609:
URL: https://github.com/apache/airflow/issues/8609#issuecomment-738978922


   Hi @kaxil and @ashb,
   Me and @Cabeda just made the test under version 2.0.0beta3 and it still exists.
   Here is how to we replicated it:
   1. Install version 2.0.0beta3 via Docker;
   2. _(the following are always using Airflow)_
   3. Create in another user called "test_user", besides having the "Admin" user;
   4. Create role "test_role";
   5. Remove all roles from user "test_user" and assign role "test_role" to it;
   6. Change DAG "example_bash_operator" code to account with `access_control={'test_role': ['can_edit', 'can_read']},` inside the `DAG()` constructor;
   7. See the DAG code change as an Admin logged in;
   8. Log out and log in as "test_user";
   9. **You don't see the DAG as it was expected**;
   10. Log out and log in as "Admin";
   11. Click the refresh button of the "example_bash_operator" DAG;
   12. Log out and log in as "test_user";
   13. Now you see the DAG.
   
   Hope this helps tackling it. This one is really impacting our BAU when using Airflow.
   If we can help in any other way. Let us know!


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org