Open zedtux opened 5 years ago
The intent on passwords it is for people to configure key based authentication (https://www.ssh.com/ssh/key/)
The code mostly tries to keep ssh sessions to a minimum but doesn't get too crazy.
As for the license, I really can't tell you much. I haven't used chef in nearly 10 years at this point. Probably time to deprecate the gem entirely.
Gonna call this the last straw
I've updated the readme to indicate the deprecation. knife-zero looks somewhat more maintained so might hold an answer for you regarding the licensing.
If not, hopefully someone from Chef proper can point you in the right direction.
Probably time to deprecate the gem entirely.
😨
What are you using instead, and why aren't you using Chef/Knife solo anymore?
At my day job I mostly use ansible.
For personal stuff I tend toward https://aws.amazon.com/elasticbeanstalk/ or if I need to run outside AWS I'd probably be looking at a hosted kubernetes option, or ansible for raw hosts.
Also hope you don't take my response as critical here.
Please know I appreciate the github issue report. But you've brought my attention to this new licensing flow in chef.
This has made it quite clear knife-solo has drifted too far away from current chef workflows over the last decade since I've stopped actively using it. Gotta know when to fold 'em.
Well I'm using Chef to provision the nodes with Kubernetes actually.
So I guess you're using Ansible to provision k8s?
We chose Chef because of its flexibility thanks to the Ruby code and for all the available cookbooks. Ansible looks great, but seemed like the YAML format was limiting the flexibility, does it?
Not k8s, but our internal scheduler. Probably k8s soon ;)
I wouldn't say the YAML's particularly limiting and I find I often just drop to bash+cli tooling anyway (both today in ansible and when I was doing chef).
My only real complaints with ansible have been:
it's oddly slow to do certain tasks (e.g., copy from workstation, user/group management) - so we often just shell
what we need to do
it's quite chatty so latency between workstation & host compounds total run time - we drive via rundeck to help avoid this.
if a few hosts out of the fleet are slow to converge, it can be hard to figure out which one and why - but knife-solo is single host anyway, so no comparison there.
The issue
I'm new to knife solo and I'm trying to run the following command on a fresh Debian 9 VPS :
Here I'm running the bootstrap with the
--yes
flag, but it didn't change anythingFirst point is I have to enter my root password many times. Second point and the main point of this issue is that I can't accept the licence agreement even typing
y
oryes
.I'm using
zsh
5.7.1 on a up-to-date macOS machine, withssh -V
outputtingOpenSSH_7.9p1, LibreSSL 2.7.3
.A start of investigation
Now connecting to the node, running manually the
chef-client
command prints the same thing :Looking in the Chef documentation I found the
--chef-license
flag which solve the issue :