infrastructure for service providers implementation

Would make sense to have a generic support in ParseServer for communication services, like mailgun, twillio,etc, based on generic configuration infrastructure parameters ?

like :

var api = new ParseServer({
  databaseURI: databaseUri || 'mongodb://localhost:27017/dev',
  cloud: process.env.CLOUD_CODE_MAIN || __dirname + '/cloud/main.js',
  appId: process.env.APP_ID || 'myAppId',
  masterKey: process.env.MASTER_KEY || 'myMasterKey',
  providers : {
       mailGun : {
            service: 'mailgun',
            apiKey: process.env.MAILGUN_API_KEY || 'mg-MYMAILGUNKEY',
            domain: process.env.MAILGUN_DOMAIN || 'mymailgundomain@mailgun.org',
            fromAddress: process.env.MAIL_FROM_ADDRESS || 'My App <myapp@domain.com>' 
       },
      twillio : {
      }
    }
});

Instead of hardcoding providers into ParseServer (index.js) ?

parse-community / parse-server

infrastructure for service providers implementation #197