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
One of our users asked if they can use engflow_auth together with reclient. Sadly, it looks like this doesn't work. It looks like this repo supports a credential helper in credshelper.go, but the protocol is not the same.
Would you consider implementing the Bazel credential helper protocol? It would be nice to avoid incompatibility here. I'm happy to send a PR if that would be useful.
If not, is the current credential helper protocol stable? Can it be documented?
Is there any way to use the credential helper without OAuth2? Our credential helper does use OAuth2 to obtain a token in the background, but Bazel isn't aware of that, and it isn't surfaced in the credential helper protocol. We'd like to set HTTP headers to opaque strings.
The text was updated successfully, but these errors were encountered:
Hello! I'm one of the authors of
engflow_auth
, a Bazel credential helper that works with EngFlow.One of our users asked if they can use
engflow_auth
together with reclient. Sadly, it looks like this doesn't work. It looks like this repo supports a credential helper in credshelper.go, but the protocol is not the same.The text was updated successfully, but these errors were encountered: