Packaging chef tools

[Tensibai]

@Raboo

t's not secure to pipe bash scripts from internet, especially as root.

Nothing prevents you from getting the script and use it internally, as for the packages and serve them internally. (which solves your last point too)

@Raboo

You can use the one resource "apt_repository" from the apt cookbook to install chef-client if you want to do it from a coobook, or similar for RHEL using the yum cookbook.

Interesting approach, installing chef repo with chef in order to install chef

@Raboo

And you upgrade chef in the same way you upgrade everything else in your distro.. apt-get update && apt-get dist-upgrade.. No need to have a cookbook in order to do it.

I do hope you're managing your packages version better than just getting latest versions, specially for the chef-client, hence the point of using a cookbook to pinpoint the version.

@Raboo

And why would you need a script, when a package can do all that it needs to install?

It is just easier to have the same command on any machine provisonning IMO, the script just guess the machine type to get the proper package, if you want to get rid of it just see the page I linked from the documentation to get the proper package with a single curl call.

@Raboo

With a proper repository you can install chef as all the other packages you install for your distro, you can easily mirror it with pre-made tools, no need to reinvent the wheel. You can verify signatures.

This is the only valid concern thus far and it should be doable, see this post about apt-cacher-ng.

And for the repo on itself, just see the documentation and tell us what does not work with that.

Excerpt from the doc:

To set up an Apt package repository for Debian and Ubuntu platforms:

Enable Apt to fetch packages over HTTPS:

$ sudo apt-get install apt-transport-https
Install the public key for Chef Software Inc:

$ wget -qO - https://downloads.chef.io/packages-chef-io-public.key | sudo apt-key add -
Create the Apt repository source file: [...]