Description
Is your feature request related to a problem? Please describe.
Parse Config is a convenient way to remotely configure client parameters. It can also be used in Cloud Code to conveniently configure global parameters like this:
const config = await Parse.Config.get();
const myParam = config.get("myParam");
However, using Parse Config for both poses a problem, as all config parameters are exposed to the client. Cloud Code parameters are of internal nature and it may not be wanted to expose these to clients. In that case Parse Config cannot be used for Cloud Code.
Describe the solution you'd like
Implement ACL for config parameters, on a per-parameter basis.
- The default being
Public
so it would not pose a breaking change. - At least the ACL row for "Public" is required to make some parameters only accessible via
useMasterKey
in cloud code. A per-user / per-role ACL configuration could be omitted if that reduces implementation efforts.
Describe alternatives you've considered
As @davimacedo proposed, the alternative would be to create a class and configure the parameters there. This is a working but not elegant solution since we already have Parse Config for that sort of functionality.