Tiller 0.5.0 released


Note : This page may contain outdated information and/or broken links; some of the formatting may be mangled due to the many different code-bases this site has been through in over 20 years; my opinions may have changed etc. etc.

Just a quick “heads up” for users of Tiller - version 0.5.0 has just been released and has a few new features, and some other changes. Firstly, I have added support for per-environment common settings. Normally, you’d do things like enable the API, set the exec parameter and so on in common.yaml, but as per issue #10, you can now specify / over-ride these settings in your environment configuration blocks. Simply drop them under a common: section, e.g.

  api_enable: true
  api_port: 1234
  exec: /usr/bin/foo -v

This will also hopefully come in handy later on for some other plugins, such as the planned etcd integration.

There’s also two more changes, hopefully these won’t affect anyone! I’ve firstly moved to using spawn instead of the previous “fork & exec” method, as this provides many more useful options when forking the replacement process. As this method was introduced in the Ruby 1.9.x series, I have dropped support for 1.8.x and made required_ruby_version = '>= 1.9.2' a dependancy of the gem. I never properly tested on 1.8.x anyway, and decided to end implicit support given that 1.8.7 was released in 2008 and extended maintenance finally ended last year. If you’re running 1.8.x anywhere, you really should upgrade to something more recent as few projects these days support it.

Of course, if you really, really need to use Tiller under Ruby 1.8.x, you can always change the spawn call back to the old “fork & exec” method, but as time goes on I’ll probably rely on more modern Ruby features. So for now, consider this a totally unsupported hack to buy you some time. However if it causes too many problems for people, I can always look at providing switchable behaviour but I’d really like to avoid this - and it’s still unlikely that I’ll run any tests against it.