Skip to content

Ubuntu 20.04 and Chef 16 support #76

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

PowerKiKi
Copy link

@PowerKiKi PowerKiKi commented Feb 25, 2021

Drop umask in known_hosts, because it lead to a fatal error
no implicit conversion from nil to integer. And it had actually
no purpose because the file always already exist. It either
exists before Chef runs, or we create it ourselve via the file
resource with proper mode just before using execute.

known_hosts also better detect presence of host in config file
for CentOS where ssh-keygen does not print out human readable
message including "Host found".

config now supports config file that contains the Include keyword
before any Host keyword, as is seen in Ubuntu 20.04.

After merging this, I would suggest to release a 1.0.0, to clearly communicate that this cookbook is production ready and has been used as such for years now.

Drop `umask` in `known_hosts`, because it lead to a fatal error
`no implicit conversion from nil to integer`. And it had actually
no purpose because either the file always already exist. It either
exists before Chef runs, or we create it ourselve via the `file`
resource with proper `mode` just before using `execute`.

`known_hosts` also better detect presence of host in config file
for CentOS where `ssh-keygen` does not print out human readable
message including "Host found".

`config` now supports config file that contains the `Include` keyword
before any `Host` keyword, as is seen in Ubuntu 20.04.
@PowerKiKi
Copy link
Author

Oh, I probably should have mentioned that kitchen test pass.

Because it's new Chef best-practice
@PowerKiKi
Copy link
Author

@tejaycar, @markolson, are you still active for this project ? Is there a chance you would release this PR ?

If not, would you recommend forking, adding new members to the project, or using an alternative cookbook ?

@PowerKiKi
Copy link
Author

@tejaycar, @markolson, could you please either archive this repository, or add new member to continue its maintenance ?

@tejaycar
Copy link
Collaborator

tejaycar commented Jan 1, 2022

@PowerKiKi are you interested in taking over the repository? I'm many years out of the chef community, and in no position to continue maintenance. @markolson more or less handed off to me many years back and has not been very active in the repo for quite some time either.

@PowerKiKi
Copy link
Author

@tejaycar, yes I would accept an invitation to join the GitHub project and continue to maintain it in the foreseeable future (but not really add new features).

If I will be mostly the only maintainer, then it would be best if I get admin access, in order to be able setup CI and such. If that's not possible then it might be best to archive this repo and create an "official" fork.

Thank you for getting back to us and happy New year !

@tejaycar
Copy link
Collaborator

tejaycar commented Jan 3, 2022

I'm afraid this is on @markolson . I don't believe I have admin either, so I'm not able to add you to the repo.

@PowerKiKi
Copy link
Author

Thank you for your effort. I reached out to Sous-Chefs, to see if they would adopt this cookbook under their organisation. If that doesn't work out, I'll fork the cookbook permanently, either publicly at https://github.com/Ecodev/chef-ssh, or privately, depending on our internal needs...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants