v1.4.0: Updated Support for Digital Ocean & Openstack

Upstream changes

• Fix support for knife-openstack >= 1.0.0. (@fnichol)
• Fix support for knife-digtal_ocean >= 2.0.0. (@fnichol)

v1.3.0

New features

• Pull request #55: Add Digital Ocean support! (@fnichol)

v1.2.0

Upstream changes

• Pull request #48, issue #50: Fix issue affecting newer Knife/Chef versions dealing with nil default options. (@dldinternet, @fnichol)
• Patch specific versions of Chef to fix knife configure bug. (@fnichol)

New features

• Pull request #51: Add OpenStack support to knife-server command. (@johnbellone)
• Re-use existing private user key for omnibus bootstraps. (@fnichol)
• Add support for downloading packages from a URL using the --url flag. (@fnichol)

Improvements

• Pull request #43: Enable ssh on firewall. (@taylor)
• Add output when backing up and writing keys locally. (@fnichol)
• Issue #28: Shunt stderr/ioctl warnings to a tmp log file for knife configure. (@fnichol)
• Issue #9, issue #10: Validate that node_name & client_key are set when running plugins, giving the user a hint that their local knife.rb is not currently set up correctly. (@fnichol)
• Update download URL for Omnibus packages. (@fnichol)
• Update testing dependencies, upgrade to RSpec 3.x, freshen TravisCI build matrix, add style and complexity support. (@fnichol)

v1.1.0

New features

• Pull request #42: Add support for Linode (via the knife-linode gem). (@fnichol)

Improvements

• Pull request #41: Add new option pretty_print for knife server backup. (@sawanoboly)

v1.0.1

Bug fixes

• Pull request #29: Fix README typo in ssh password argument. (@ranjib)
• Pull request #34: Fix AMQP_PASSWORD propagation. (@erikh)

Improvements

• Pull request #35: Add VPC support. (@jssjr)
• Pull request #34: Provide better information when the package can't be
  downloaded. (@erikh)

v1.0.0

Breaking Changes

• Default Chef Server installed is the latest Chef 11 (erchef) version from
  Omnibus packages via the "chef11/omnibus" template. All platform supported
  by the Omnibus packages should work out of the box. Chef Server 10 is still
  supported by setting the --bootstrap-version flag to "10". (@fnichol)
• WebUI is no longer configured to start up by default (--enable-webui flag
  introduced to re-enable). For more details, please read
  http://lists.opscode.com/sympa/arc/chef-dev/2013-02/msg00023.html.
  (@fnichol)
• The knife-ec2 gem is no longer a direct dependency; you must add install this
  gem or add it to your Gemfile in order to use knife server bootstrap ec2.
  (@fnichol)

New features

• First class support for RHEL platform family nodes including CentOS,
  Scientific, RHEL, Amazon Linux, etc. Seriously, this is huge. (@danryan,
  @erikh)
• Support for installing Chef 11 (erchef) servers from Omnibus packages.
  (@fnichol)
• Add --log-level flag to help debug bootstrap template output. (@fnichol)
• Support all relevant options from Chef::Knife::Bootstrap and
  Chef::Knife::Ec2ServerCreate in the standalone and ec2 subcommands. This
  includes --bootstrap-version, ssh options, ebs options, etc. (@fnichol)
• An auto mode (set via --platform auto) which will detect the node's platform
  and run the appropriate template for Chef 10 servers. Currently only
  supported with standalone subcommand. (@erikh)

Improvements

• Ensure config parameters are applied in the right order for Chef 10/11.
  (@fnichol)
• Add matrix build support to TravisCI for multiple versions of Chef.
  (@fnichol)
• Update README badges (better consistency). (@fnichol)
• Update CHANGLOG format headings for Vandamme/Gemnasium compatability.
  (@fnichol)
• Update README documentation with 1.0.0 changes. (@fnichol)