namespace-regex config bug

[rentiansheng]

• (Unauthorized) not authorized on admin to execute command
• (Unauthorized) not authorized on config to execute command

error detail:

ERROR 2021/06/04 20:37:45 Error starting change stream. Will retry: (Unauthorized) not authorized on admin to execute command { aggregate: 1, pipeline: [ { $changeStream: { allChangesForCluster: true, fullDocument: "updateLookup" } } ], cursor: {}, lsid: { id: UUID("89609306-00c3-429d-b584-58a58da89f5d") }, $clusterTime: { clusterTime: Timestamp(1622810252, 1), signature: { hash: BinData(0, 870E8B4C26D5988646DC3131697CA1E57580750E), keyId: 6940129626588971010 } }, $db: "admin", $readPreference: { mode: "primary" } }

[patrickserrano]

@rwynn I'm seeing this too, and rough timeline on when we could see #525 merged and released? thanks!

[rwynn]

Hey @patrickserrano I'm not so sure about the direction the pull request takes. When that is applied monstache will no longer create a change stream at the deployment level. That has been the default for a long time since it means that a change to any MongoDB collection gets propogated to Elasticsearch.

The namespace-regex-config was not about selecting the collections to sync but rather to simply be a client side filter. The actually configuration for what to watch was always supposed to come from the change-stream-namespaces config which lets you select at the deployment, database, or collection level.