Micro Services: Create internal services and allowed services list

[sampaiodiego]

Proposed changes

I'm proposing a way to control if a service should be registered on network broker of rocket.chat instances, which can be controlled via two different env vars:

• INTERNAL_SERVICES_ONLY (default false) - if set to true rocket.chat will register only internal services, that are services that only rocket.chat instances have the information to respond or emit events, i.e.: meteor-service
• SERVICES_ALLOWED (default empty) - a comma separated list of services that when set will control which service will be registered on the rocket.chat instance, it has precedence over the INTERNAL_SERVICES_ONLY which means if you set INTERNAL_SERVICES_ONLY=authorization it will not even start meteor-service

Services are considered "external" by default, which means they're by default designed to run as standalone. Maybe the flag should be called standalone, wdyt?

Issue(s)

How to test or reproduce

Screenshots

Types of changes

• Improvement (non-breaking change which improves a current function)

Checklist

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if applicable)
• I have added necessary documentation (if applicable)
• Any dependent changes have been merged and published in downstream modules

Changelog

Further comments