[
https://issues.apache.org/jira/browse/AIRFLOW-2267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16545694#comment-16545694
]
ASF subversion and git services commented on AIRFLOW-2267:
----------------------------------------------------------
Commit f3f2eb323f29d2210877ce9699e2dd0bdd8b5259 in incubator-airflow's branch
refs/heads/master from Tao feng
[ https://git-wip-us.apache.org/repos/asf?p=incubator-airflow.git;h=f3f2eb3 ]
[AIRFLOW-2267] Airflow DAG level access
Make sure you have checked _all_ steps below.
### JIRA
- [x] My PR addresses the following [Airflow JIRA]
(https://issues.apache.org/jira/browse/AIRFLOW/)
issues and references them in the PR title. For
example, "\[AIRFLOW-XXX\] My Airflow PR"
-
https://issues.apache.org/jira/browse/AIRFLOW-2267
- In case you are fixing a typo in the
documentation you can prepend your commit with
\[AIRFLOW-XXX\], code changes always need a JIRA
issue.
### Description
- [x] Here are some details about my PR, including
screenshots of any UI changes:
Provide DAG level access for airflow. The detail
design could be found at https://docs.google.com/d
ocument/d/1qs26lE9kAuCY0Qa0ga-80EQ7d7m4s-590lhjtMB
jmxw/edit#
### Tests
- [x] My PR adds the following unit tests __OR__
does not need testing for this extremely good
reason:
Unit tests are added.
### Commits
- [x] My commits all reference JIRA issues in
their subject lines, and I have squashed multiple
commits if they address the same issue. In
addition, my commits follow the guidelines from
"[How to write a good git commit
message](http://chris.beams.io/posts/git-
commit/)":
1. Subject is separated from body by a blank line
2. Subject is limited to 50 characters
3. Subject does not end with a period
4. Subject uses the imperative mood ("add", not
"adding")
5. Body wraps at 72 characters
6. Body explains "what" and "why", not "how"
- [x] Passes `git diff upstream/master -u --
"*.py" | flake8 --diff`
Closes #3197 from feng-tao/airflow-2267
> Implement DAG-level access for airflow
> --------------------------------------
>
> Key: AIRFLOW-2267
> URL: https://issues.apache.org/jira/browse/AIRFLOW-2267
> Project: Apache Airflow
> Issue Type: Improvement
> Reporter: Tao Feng
> Assignee: Tao Feng
> Priority: Major
>
> Now we have a new airflow UI based on RBAC, we would like to implement per
> DAG-level access on top of it. I have started some initial discussions with
> Max @mistercrunch, and will come up with a proposal shortly to gather more
> feedback from the community.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
