P.S.: Is there good reason for this limitation? I never watch the entire db but collections only. Seems like being able to store Monstache configs in same db should be fine. Would be much neater too in deployments with stringent access control, where requirement for provisioned databases suddenly doubles from 1 to 2.
Add extra info to config-database-name with limitation that has caught me out.
Based on: https://github.com/rwynn/monstache/issues/474#issuecomment-759119028
P.S.: Is there good reason for this limitation? I never watch the entire db but collections only. Seems like being able to store Monstache configs in same db should be fine. Would be much neater too in deployments with stringent access control, where requirement for provisioned databases suddenly doubles from 1 to 2.