In setups where different users or environments have different access permissions on collections/databases, relations can point to a collection the current user isn't authorized to access. This is a fairly common scenario (e.g. shared relation definitions across users with varying permission levels), and in that case an error like the following gets shown every time the relation is resolved:
Error getting related documents: MongoServerError: not authorized to execute command { find: "", filter: {...}, projection: {...}, ... }
Since this is an expected condition rather than an actual bug, it would be great to have an option to suppress or silently skip these "not authorized" errors when resolving relations, or at least downgrade them to a quiet log/warning instead of a user-facing error.
Thanks for considering this!
In setups where different users or environments have different access permissions on collections/databases, relations can point to a collection the current user isn't authorized to access. This is a fairly common scenario (e.g. shared relation definitions across users with varying permission levels), and in that case an error like the following gets shown every time the relation is resolved:
Error getting related documents: MongoServerError: not authorized to execute command { find: "", filter: {...}, projection: {...}, ... }
Since this is an expected condition rather than an actual bug, it would be great to have an option to suppress or silently skip these "not authorized" errors when resolving relations, or at least downgrade them to a quiet log/warning instead of a user-facing error.
Thanks for considering this!