We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I want to run libspecinfra on CI services (e.g. Circle CI) and FaaS (e.g. AWS Lambda). These services may be difficult to use ssh-agent.
So, I would like to implement the another way to use SSH backend that specify the host, user and key file or password.
@mizzy What do you think about these options?
First,
Next, (Only if we choice 1 at first)
1
backend_ssh_new
The text was updated successfully, but these errors were encountered:
Thanks for your proposal.
Change SSH backend to be able to use without ssh-sgent
This one is best.
Change the argument of the backend_ssh_new cffi interface to a structure. This is very simple. But it has a breaking change.
We don't need to care backward compatibility currently. So this idea is good.
Sorry, something went wrong.
I'm glad to hear that. Thanks!!
Change SSH backend interface to a struct with pubkey/password libspec…
81bba7d
…infra#43
No branches or pull requests
Hi,
I want to run libspecinfra on CI services (e.g. Circle CI) and FaaS (e.g. AWS Lambda).
These services may be difficult to use ssh-agent.
So, I would like to implement the another way to use SSH backend that specify the host, user and key file or password.
@mizzy What do you think about these options?
First,
Next, (Only if we choice
1
at first)backend_ssh_new
cffi interface to a structure. This is very simple. But it has a breaking change.The text was updated successfully, but these errors were encountered: