Parse Server options should set default

[dblythy]

New Feature / Enhancement Checklist

• I am not disclosing a vulnerability.
• I am not just asking a question.
• I have searched through existing issues.

Current Limitation

Currently, to add Parse Server options, developers have to add validation for the variable type, as well as set the default. The error messages for if a variable doesn’t enforce a type is inconsistent. And, you cannot set environment variables to deep Parse Server options. Overall, it needs some TLC.

Feature / Enhancement Description

All this information is already typed in the definitions, so the type and default should be automatically set. The only custom validation should be for stricter rules, such as checking that a parameter is greater than 0, for example.

Example Use Case

Creating a new server option would require much less code if the type handling and defaults were handled internally.

Alternatives / Workarounds

Related: #7151

3rd Party References

n/a

[parse-github-assistant]

Thanks for opening this issue!

• 🎉 We are excited about your ideas for improvement!

[dblythy]

Parse Server should also log an error when an unsupported config option is set, such as "massterKey".

[mtrezza]

I am not very fond of Parse Server's current options implementation. Our home-cooked implementation is already overly complex and has issues. Maybe we can look at that in the context of #7069 and replace it with a standardized options framework.