arollet22 commented on issue #45738: URL: https://github.com/apache/airflow/issues/45738#issuecomment-2721104245
Maybe I can jump in to answer that question. We are also experiencing the same issue. What happens generally is the Airflow dev forgets to set the correct ACL during the first run, faces a permission issue on the Databricks UI and doesn't understand why its updated ACL configuration doesn't fix the problem. (Usually Airflow workflows/jobs are created using Service Principals which do not grant any rights by default to the group / users). One other use case I can imagine, although not faced yet, is if you were to migrate a workflow ownership to another group. The consequence is not that the job doesn't run, that works well, but if one task fails then the dev isn't able to check the logs to correct the error. -- 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]
