-
Notifications
You must be signed in to change notification settings - Fork 13.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(security): Remove obsolete FAB metric_access permission #16860
chore(security): Remove obsolete FAB metric_access permission #16860
Conversation
Codecov Report
@@ Coverage Diff @@
## master #16860 +/- ##
==========================================
+ Coverage 66.35% 68.91% +2.56%
==========================================
Files 1569 1613 +44
Lines 61692 69565 +7873
Branches 6240 6240
==========================================
+ Hits 40934 47943 +7009
- Misses 19161 20025 +864
Partials 1597 1597
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@john-bodley this is a custom Superset permission and not a FAB one, FAB will only cleanup registered Flask methods on BaseViews
, it will not manage unknown permissions that exist on the DB. So on this case would be nice to add a migration to cleanup
9745de1
to
7322703
Compare
* Update manager.py * Update manager.py * Update manager.py * Update manager.py (cherry picked from commit 85f0715)
SUMMARY
Per here the
metric_access
permission is obsolete and not used anywhere.Note I assume that FAB should clean up after itself and thus no explicit migration is necessary.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
CI.
ADDITIONAL INFORMATION