Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Project clone init container should respect sshkeys and gittokens #400

Closed
sleshchenko opened this issue Apr 28, 2021 · 1 comment · Fixed by #492
Closed

Project clone init container should respect sshkeys and gittokens #400

sleshchenko opened this issue Apr 28, 2021 · 1 comment · Fixed by #492
Assignees
@amisevsk
Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Milestone
v0.8.0

Comments

@sleshchenko
Copy link
Member

Project clone now can handle only publicly available repos, we need to make it using sshkeys and gittokens from secret (probably which are annotated in a special way)
@sleshchenko sleshchenko mentioned this issue Apr 28, 2021
Closed
2 tasks
@amisevsk
Copy link
Collaborator

IMO this depends on #384

@sleshchenko sleshchenko mentioned this issue Jul 9, 2021
Closed
16 tasks
@sleshchenko sleshchenko added sprint/current Is assigned to issues which are planned to work on in the current team sprint and removed sprint/next labels Jul 9, 2021
@sleshchenko sleshchenko added this to the v0.8.0 milestone Jul 9, 2021
@amisevsk amisevsk self-assigned this Jul 15, 2021
@amisevsk amisevsk mentioned this issue Jul 15, 2021
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@amisevsk amisevsk

Labels
sprint/current Is assigned to issues which are planned to work on in the current team sprint
Projects
None yet
Milestone
v0.8.0
Development

Successfully merging a pull request may close this issue.

Use git binary for fetch to make ssh easier amisevsk/devworkspace-operator
2 participants
@sleshchenko @amisevsk