The problem here is that Operations doesn’t provide the config to custom Context implementations, otherwise this would be fine. Schemas/tenants is a perfectly fine approach for mutli-tenancy with small numbers of tenants but proven to be unmaintainable once in the thousands, which is why a more straightforward referential namespacing is desirable.
Would you be open to a PR that conditionally supplies the config to a custom user_context if the functions support the extra argument? It seems strange to me that Pow.Ecto.Context receives the argument but an implementation of it doesn’t.
