Is your feature request related to a problem? Please describe.
Using the server-level TaskStore to interface with external systems doesn't work if that interfacing depends on using user-level auth, such as RLS-based database systems.
Describe the solution you'd like
Ideally, authInfo as well as other metadata about a given request could get passed to the TaskStore, either in the constructor or as an additional parameter for all methods (not just creating tasks).
Describe alternatives you've considered
The workaround I'm using for the moment is to have a class that implements TaskStore but has a constructor that takes authInfo (plus anything else), then use that in createTask etc instead of the server-level TaskStore implementation.
Is your feature request related to a problem? Please describe.
Using the server-level TaskStore to interface with external systems doesn't work if that interfacing depends on using user-level auth, such as RLS-based database systems.
Describe the solution you'd like
Ideally, authInfo as well as other metadata about a given request could get passed to the TaskStore, either in the constructor or as an additional parameter for all methods (not just creating tasks).
Describe alternatives you've considered
The workaround I'm using for the moment is to have a class that
implements TaskStorebut has a constructor that takesauthInfo(plus anything else), then use that increateTasketc instead of the server-level TaskStore implementation.