Yaybu

-------------------

- Initial subversion checkouts are no longer quiet - to match 'svn up'
behaviour - this is useful for large checkouts when you arent sure if the
checkout has hung.

- Use of 'svn' without having subversion installed will trigger a propper error
instead of a traceback. Both this and the rsync checks now have a proper
exception for reporting missing dependencies.

- Service[] now parses the output of ``/sbin/status`` to determine if an
upstart job is running or not. It considers the goal of the job to determine
if it needs to adjust the job. For example, we might want to start a job and
that job isn't running, but it is starting. That is good enough, so Yaybu
wouldn't take any action.

A side effect of implementing proper state detection is that when trying to
restart an upstart job that was stopped now just starts the job directly.

- Adds version information to the command line interface

- The protocol Yaybu uses for communicating over SSH has grown some version
metadata. This will be used to ensure better interoperability between Yaybu
clients and targets.

**WARNING** You will need to ensure your clients and servers are running at
least this version as this is (hopefully the last) protcol breaking change.

- Reclassifies some log output as debug information for quieter deployments
when nothing has changed.

-------------------

- Add a dummy Checkout provider that uses rsync. The primary use case for this
feature is vagrant where you can do something like this::

resources.append:
- Checkout:
name: /var/checkouts/my-site
repository: /vagrant
scm: rsync
user: vagrant

- Execute:
name: buildout
command: ./buildout
cwd: /var/checkouts/my-site
policy:
execute:
- when: sync
on: Checkout[/var/checkouts/my-site]

There are 2 advantages here: firstly, your production config will likely
deploy from Git, but Vagrant always gives you a /vagrant directory without
having to have a seperate Git checkout. With this change you can still use a
Checkout resource for your /vagrant sourced code, keeping your recipes as
similar as possible. Secondly, your ``vagrant provision`` will be able to
detect code changes just like a real Checkout. For example, you can add
watches to restart services when you change a particular script or asset in
your 'checkout'.

- The default mode for directories is now 0755.

- Improve cross-platform support by not making assumptions about the value of
sys.maxunicode.

- Use yay 0.0.39 to avoid some pickle issues.

-------------------

- A Subversion checkout will now understand and happily use data passed to it
as String objects. This means if you use the ``scm_password`` attribute it
won't leak your password into the logs.

- We now depend on Yay 0.0.35 for the improved ``String`` API.

- The subprocess abstraction natively supports ``String`` instances and will
mask any secrets in log output. It now also supports native strings and
will shlex.split them automatically.

-------------------

- Yabyu now depends on Yay 0.0.33 and the improved ``Openers()`` API. This means
that cookbook assets can be fetched from any location that Yay can be fetched
from, including http and https.

- This change also means that Yay loading also respects the YAYBUPATH, and that
http content can be on the YAYBUPATH.

- Fix python-magic fallback - in previous version the fallback was inverted and
claiming all text was binary

------------------

- Add a basic docs for Vagrant provisioner.
- Add a better fallback for when 'python-magic' isn't installed

------------------

- Allow ``set_interactive`` call on RemoteRunner for batch processing use cases
- Allow API users to set a particular identity file with set_identity_file
- Change Context object to parse userhost:port into individual variables
This fixes ${yaybu.host} containing user and ports details.