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

Support SSH keys as secrets #32083

Open
rarkins opened this issue Oct 22, 2024 · 1 comment
Open

Support SSH keys as secrets #32083

rarkins opened this issue Oct 22, 2024 · 1 comment
Labels
core:config Related to config capabilities and presets priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others

Comments

@rarkins
Copy link
Collaborator

rarkins commented Oct 22, 2024

Describe the proposed change(s).

Sometimes users have git dependencies - including submodules - which are authenticatable only using ssh and not https. We should find a way for users to provide a private SSH key to Renovate.
@rarkins rarkins added priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others core:config Related to config capabilities and presets labels Oct 22, 2024
@viceice
Copy link
Member

viceice commented Oct 23, 2024

I think the easiest solution is to start the key agent, add the keys, process repo (pass key agent env as required), stop agent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
core:config Related to config capabilities and presets priority-3-medium Default priority, "should be done" but isn't prioritised ahead of others
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@viceice @rarkins