[
https://issues.apache.org/jira/browse/AIRFLOW-3271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16669322#comment-16669322
]
ASF GitHub Bot commented on AIRFLOW-3271:
-----------------------------------------
smithakoduri opened a new pull request #4118: [AIRFLOW-3271]Fix is added to not
reset the database whenever a new…
URL: https://github.com/apache/incubator-airflow/pull/4118
… process comes up (or init_roles is called). Otherwise Airflow RBAC
permissions that are modified, do not persist for long
Make sure you have checked _all_ steps below.
### Jira
- [ ] 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-XXX
- 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
- [ ] Here are some details about my PR, including screenshots of any UI
changes:
### Tests
- [ ] My PR adds the following unit tests __OR__ does not need testing for
this extremely good reason:
### Commits
- [ ] 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
1. Subject is limited to 50 characters (not including Jira issue reference)
1. Subject does not end with a period
1. Subject uses the imperative mood ("add", not "adding")
1. Body wraps at 72 characters
1. Body explains "what" and "why", not "how"
### Documentation
- [ ] In case of new functionality, my PR adds documentation that describes
how to use it.
- When adding new operators/hooks/sensors, the autoclass documentation
generation needs to be added.
### Code Quality
- [ ] Passes `flake8`
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Airflow RBAC Permissions modification via UI do not persist
> -----------------------------------------------------------
>
> Key: AIRFLOW-3271
> URL: https://issues.apache.org/jira/browse/AIRFLOW-3271
> Project: Apache Airflow
> Issue Type: Bug
> Reporter: Smitha Koduri
> Assignee: Smitha Koduri
> Priority: Major
>
> After upgrading Airflow to 1.10, we have noticed that when attempting to add
> a new permission-role mapping (via UI), initially it gets successfully added
> to db. But later, the entry doesn't persist in the db.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
