-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
add key_file path option #222
Comments
It would seem the best way to do this would be: If the key_file was provided, run:
The one question I have is would it be enough to only issue the command in the Assuming Having it in both places may be confusing and preceived as required..... |
If it is in just retrieve I would at least make note in the documentation on publish that it is an option inherited from retrieve |
+1. I'm not sure if I'm missing something in the options documented for the module but how exactly is the key file supplied for this module as implemented right now? |
Was there any solution provided? |
It's been a while since I messed with this but if I remember correctly, if you use the retrieve module there is a way to add a key file info which would be used on publish module |
SUMMARY
it would be really helpful if you could add a key_file path option to the modules to point to specific private key file to gain permissions to private repos.
ISSUE TYPE
COMPONENT NAME
ADDITIONAL INFORMATION
to allow easier usage of private key files to access private repos
The text was updated successfully, but these errors were encountered: