Skip to content

Conversation

@soltysh
Copy link

@soltysh soltysh commented May 4, 2015

@adellape
Copy link
Contributor

adellape commented May 4, 2015

Related docs card: https://trello.com/c/nsFhtpIV

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/In case you/If you/

@bparees
Copy link
Contributor

bparees commented May 4, 2015

couple minor fixes and one medium size suggestion, otherwise looks good!

@soltysh
Copy link
Author

soltysh commented May 5, 2015

@bparees addressed all your comments.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/sshsecert/sshsecret/

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It'll be changed to ssh-privatekey based on discussion here.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@soltysh Just to confirm, when sshsecret is changed to ssh-privatekey, will ssh-privatekey be specifically what is required for this, like the dockercfg key in the previous section? I'm assuming so based on the "Supported auth methods are: ssh-privatekey" comments in the linked dev PR.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that's correct, based on the key name we'll choose the appropriate auth method. For now ssh-privatekey is the only supported, future versions will support user+password and token etc. I'll update that PR as soon as my code PR is done, which I'm pretty close to.

@bparees
Copy link
Contributor

bparees commented May 5, 2015

couple more comments.

@soltysh
Copy link
Author

soltysh commented May 8, 2015

@bparees updated & addressed your comments. PTAL.

@bparees
Copy link
Contributor

bparees commented May 8, 2015

looks good to me, excellent work @soltysh!

@soltysh
Copy link
Author

soltysh commented May 8, 2015

@bparees thx, I have good reviewers 😄

@adellape
Copy link
Contributor

adellape commented May 8, 2015

@soltysh I'm assuming I should wait til the code PR merges before merging this. I'll slap a [do not merge] on this until told otherwise. Thanks!

@adellape adellape changed the title Card origin_devexp_286 - Added ssh key-based access to private git repository documentation [do not merge] Card origin_devexp_286 - Added ssh key-based access to private git repository documentation May 8, 2015
@bparees
Copy link
Contributor

bparees commented May 8, 2015

yeah, you'll want to wait on this PR: openshift/origin#1926

@soltysh
Copy link
Author

soltysh commented May 11, 2015

@adellape the PR @bparees mentioned is merged, you can safely merge this one as well.

@adellape adellape changed the title [do not merge] Card origin_devexp_286 - Added ssh key-based access to private git repository documentation Card origin_devexp_286 - Added ssh key-based access to private git repository documentation May 11, 2015
adellape added a commit that referenced this pull request May 11, 2015
Card origin_devexp_286 - Added ssh key-based access to private git repository documentation
@adellape adellape merged commit e11dabb into openshift:master May 11, 2015
@soltysh soltysh deleted the card286 branch May 12, 2015 09:54
sbeskin-redhat pushed a commit to sbeskin-redhat/openshift-docs that referenced this pull request Oct 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants