ashb commented on issue #10469: URL: https://github.com/apache/airflow/issues/10469#issuecomment-686422184
> Airflow.can_extra_links => Dag.can_edit That should be `Dag.can_read` I think. > Airflow.can_index The one possible advantage of this is it's useful in some cases - for instance https://github.com/apache/airflow/pull/4973 where the they wanted public user to have access to the home page, but no DAGs. > Airflow.can_refresh => Dag.can_read Do we even need the refresh button anymore with DAG serialization? (Are we making that default/only option for 2.0?) > * **Edit/read for DAGs** - (ex. `domain: example_branch_dop_operator_v3, permission: can_dag_read`) - Change to `can_edit` and `can_read` for the same `example_branch_dop_operator_v3` domain. What specifically are we calling the permssion and view menu for dag-level permissions? `"can_read" on "dag.example_branch_dop_operator_v3" (i.e. view menu name becomes `"dag.example_branch_dop_operator_v3"`?) ---------------------------------------------------------------- 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: [email protected]
