sks
sks
cc: @rithujohn191 / @srenatus
@srenatus : My initial thought was to have limited access to connectors. But as i think about it more, it could be okay. But did not want to expose the...
~Not sure how to get the latest `protoc` and use V3,~ ~I ran `make proto`, but it still generated the V2 API :/~ ~Checking further~ Fixed in e8ab80ca0f9bae8063fea8e9b915ab8f1c8d5606, ``` git...
@srenatus : please :) Thank you for maintaining the project , I am trying to do my part while solving my own problems :)
Hi @srenatus / @bonifaido, Not sure what needs to be done so as to get a closure on this one.\ I have been maintaining a fork with this change for...
> What's your use case for it Similar to @jpatters , our use case was in a multi-tenant environment, we wanted to add new connectors when onboarding new tenants.
@sagikazarmark : Thank you for your contribution in cleaning up the `proto` clutter. I have made the changes in `api/v2/api.proto` and the changes got copied over to `api/api.proto` as soon...
I have updated the branch with the latest from `dex/master`, Please let me know in case I have missed on anything
@nabokihms / @sagikazarmark : ping please let me know how we can get this PR to closure. --Thanks Sabith
As a golang dev, I dont really care about this vuln. (Not even sure how this would pan out). but since the upgrade wont cause a regression, I thought I...