Skip to content
This repository was archived by the owner on Jan 19, 2018. It is now read-only.

Conversation

surajssd
Copy link
Collaborator

Added cert param so that now we can pass client side certs while making request to API server, this can be passed as path to file that contains cert and key or it can be a tuple which has path ti cert and key.

This is part of the effort to add support to authenticate to server via cert in addition to access_token.

Added cert param so that now we can pass client side certs
while making request to API server, this can be passed as
path to file that contains cert and key or it can be a tuple
which has path ti cert and key.

This is part of the effort to add support to authenticate to
server via cert in addition to access_token.
@centos-ci
Copy link
Collaborator

Can one of the admins verify this patch?

3 similar comments
@centos-ci
Copy link
Collaborator

Can one of the admins verify this patch?

@centos-ci
Copy link
Collaborator

Can one of the admins verify this patch?

@centos-ci
Copy link
Collaborator

Can one of the admins verify this patch?

@surajssd
Copy link
Collaborator Author

This will fix #693 and add to effort going on with #533

@dustymabe
Copy link
Contributor

Hey @surajssd this looks great but let's create a PR that solves #533 and includes this commit. You can open a WIP (work in progress) PR if you'd like show progress and gather feedback.

Also, you don't need an issue in order to create a PR. Just open the PR :-P

@surajssd
Copy link
Collaborator Author

@dustymabe I and @kadel had a discussion and we decided to work on this together, so we divided the tasks into sub-tasks which can be done in separate PRs. I feel that will introduce less bugs, compared to adding a large chunk of code once. Please suggest.

@cdrage
Copy link
Member

cdrage commented Apr 13, 2016

@surajssd Ideally it would be best if one of you just submit the major PR and if you need to change parts of the code you can send a .patch to @kadel for him to edit the code :) This would prevent any major breakage as we'd have to implement and merge in two separate PR's ideally at the same exact time.

@dustymabe
Copy link
Contributor

while I have not done this before I think it is possible to do:

you can allow push access to your fork from Tomas and then you can both push changes to the PR that you submit (by updating commits on the branch in your forked repo). If both of you have push access to your repo then you should be able to do that without any issue.

@rtnpro
Copy link
Contributor

rtnpro commented Apr 15, 2016

On Apr 14, 2016 12:00 AM, "Dusty Mabe" [email protected] wrote:

while I have not done this before I think it is possible to do:

you can allow push access to your fork from Tomas and then you can both
push changes to the PR that you submit (by updating commits on the branch
in your forked repo). If both of you have push access to your repo then you
should be able to do that without any issue.

:+1 This should just work fine.

@surajssd
Copy link
Collaborator Author

surajssd commented Apr 18, 2016

Closing this PR in response to the PR that @kadel sent #696

@surajssd surajssd closed this Apr 18, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants