Diego Sucaria
Diego Sucaria
I've been having the same issue since 4.5.0
Same issue, upgraded from 3.12.X to 4.0.1
Thanks for considering my idea! The main goal of this is that I could give another person a shell inside a container, without giving access to the rest of the...
Yes, that is exactly what I am trying to do... It could be two things: **1- single shell startup** (it could be sidecar or not): just open the shell in...
Yes, I couldn't agree more! I'll keep working on my tests and I'll share a PR if I reach something useful :) Thank you!
Hello, I'm facing the same issue here. I did rs.slaveOk() on each pod, however, that only worked for a while, and after that, the error came back. Any ideas how...
Hi there! This would be a nice feature to have. I'm facing a similar situation, using a distributed logging mechanism and need to access the express request context inside the...
@thomseddon what do you think if we add an optional "express context" parameter to all of the prototypes (authenticate, token...) Like `token(request, response, options, context)` and then pass that context...
In case someone is interested, here you can find the fork: https://github.com/diegosucaria/node-oauth2-server basic usage: ``` ... oauth.token(request, response, null, null, req).then((token)=> { ... oauth.authenticate(request, response,{scope: scopes}, null, req).then((token)=> { ```...
Was someone able to deploy this in 1.16? I tried replacing the deprecated apis on the operator itself without luck.