phani8996 opened a new pull request #4193: Fix showing config on RBAC UI when 
expose_config is False
URL: https://github.com/apache/incubator-airflow/pull/4193
 
 
   RBAC UI does not respect variable `expose_config` in airflow config to show 
configuration.
   This snippet will show config only when `expose_config` is set to `True`.
   
   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-3352\] My Airflow PR"
     - https://issues.apache.org/jira/browse/AIRFLOW-3352
   
   ### Description
   
   - [x] Here are some details about my PR, including screenshots of any UI 
       - This PR will control showing airflow configuration RBAC UI based on 
variable `expose_config` defined in airflow config
       - Please find attached screenshot for the same 
   
   
   ### Tests
   
   - [x] My PR  does not need testing as this is UI change.
   
   
   ### 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
     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"
   
   ### Code Quality
   
   - [x] 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:
us...@infra.apache.org


With regards,
Apache Git Services

Reply via email to