pm2 start config.js file which only starts some of the processes

So currently we have a config.js file which exports a list of {apps} which pm2 takes and starts up (pm2 start core.config.js).

However some of these must not actually be started. In other words it must start in a downed state.
This is cause if a client manually sets certain services(processes) to be off, pm2 must not start them but they should still be visible on pm2 status but as “Stopped” or “disabled”

pm2 status with a process down

Example would be the integrationMicroService in the image