You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some authentication methods, such as the device code login require the user to open a link on the browser, enter a code, and only then the auth command returns the token.
It doesn't seem like kube-rs currently support this as the auth_exec function doesn't give us the output of the command, it simply hangs on let out = cmd.output() because the Command never exits as it's waiting for external action.
Describe the solution you'd like
I honestly can't think of how this can be solved, so I'm just opening this to get some feedback.
Maybe, not sure if doable: return the output of the command to the caller and let us decide what to do with it (in my case I'd print this to the user, they'd navigate to that link, and the command would eventually return 0 and a token).
Describe alternatives you've considered
Couldn't think of any other, but I'm open to suggestions!
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-client
The text was updated successfully, but these errors were encountered:
Would you like to work on this feature?
maybe
What problem are you trying to solve?
Some authentication methods, such as the device code login require the user to open a link on the browser, enter a code, and only then the auth command returns the token.
It doesn't seem like kube-rs currently support this as the
auth_exec
function doesn't give us the output of the command, it simply hangs onlet out = cmd.output()
because the Command never exits as it's waiting for external action.Describe the solution you'd like
I honestly can't think of how this can be solved, so I'm just opening this to get some feedback.
Maybe, not sure if doable: return the output of the command to the caller and let us decide what to do with it (in my case I'd print this to the user, they'd navigate to that link, and the command would eventually return 0 and a token).
Describe alternatives you've considered
Couldn't think of any other, but I'm open to suggestions!
Documentation, Adoption, Migration Strategy
No response
Target crate for feature
kube-client
The text was updated successfully, but these errors were encountered: