stephenonethree commented on issue #8609: URL: https://github.com/apache/airflow/issues/8609#issuecomment-1028154067
I saw something similar on 2.1.4 - I created a DAG with a couple new roles, and expected the roles to be created and populated once the code was added. That did not happen so I clicked refresh on the DAG. This produced an error message, "The access_control mapping for DAG 'DAG:mydagname' includes a role named 'myrolename', but that role does not exist" So then I created blank roles in the UI and clicked Refresh on the DAG again, and then it worked. It seems like there might be two improvements that could be made here: 1) Create roles if they show up in a DAG and don't exist yet, 2) When there's some error related to parsing access control, show it on the DAG page to reduce confusion. Not sure of course if there is a downside to auto-creating roles rather than requiring that to be done through the UI, but I suppose most people will want to control things through the code. -- 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]
