Backend: EKS + DocDB Elastic yields Mongoose distinct undefined error
Hey there.
[maintainer akhilmhdh]: Hey there. 1. I guess both will work in mongoose await, its just error returned will be more detail for the exec one. Thus that's not an issue the call is getting executed. 2. So i guess for someversions of mongo the distinct would be undefined. I guess we need to do an undefined check . so that it doesn't fail. This is my inference. @maidul98
Context: Issue infisical/infisical#796 (closed, 14 comments): ### Describe the bug Hey! I'm executing a nuanced PoC for Infisical in EKS (AWS-hosted Kubernetes), and wanted to leverage a DocumentDB elastic cluster in lieu of an in-cluster mongo pod with persistence, to try and centralize DB management. The latest DocDB cluster specification is highly compatible with MongoDB 3, 4, and 5, so I figure it should be okay. Maybe. This is in reference to the v0.23.3 Docker images from yesterday as-of-writing. In the backend specifically, after wrestling with giving the app the correct MONGO_URL to get Mongoose to connect to the DocDB cluster succ
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.