-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Fix #5678 #5681
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
Fix #5678 #5681
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5681 +/- ##
==========================================
- Coverage 94.19% 94.16% -0.03%
==========================================
Files 129 129
Lines 9248 9240 -8
==========================================
- Hits 8711 8701 -10
- Misses 537 539 +2
Continue to review full report at Codecov.
|
while this fix seems fine, my question at this point is: what do we get out of including the mysql in server info? Thinking about why this is an issue, I'm pretty convinced that a production deployment should never allow the parse-server to ask this question as the parse-server doesn't need and shouldn't have the rights. cc: @oallouch |
I understand. Hope I can help with something else. |
* Fix parse-community#5678 * Revert "Fix parse-community#5678" This reverts commit 106b6dd. * revert parse-community#5627
No description provided.