fix(client): avoid git remote deletion for apps specified by -a
fix(deisctl): prevent build on windows

On windows the deisctl client will build, but it runs into a lot of
problems at runtime due to limitations in fleetctl. It depends on the
ssh-agent domain socket which cannot exist in windows as windows does
not support the idea of domain sockets.

This will prevent issues at runtime at the expense of being able to
build and run deisctl in windows.
fix(gateway): wait until radosgw is accessible
docs(contrib): Clarify source of DEV_REGISTRY IP Address
feat(builder): do not lookup the remote host in ssh connections
fix(builder): the value could be a number
chore(release): update version in master to 1.2.0-dev
feat(vagrant): check for discovery url
fix(controller): set config as the issuing user

When you created new config values, the previous config's owner would
become the creator of this config. Removing this line allows the
request's user to become the owner.
test(controller): ensure config owner is requesting user
feat(client): add "--buildpack" option to "deis create"

Adds option "--buildpack" (and shortcut "-b") to the "deis create"
command. This allows setting the buildpack url when creating a new app
in the same manner as the "heroku" command line tool.
test(client): add --buildpack tests
fix(client): update PyInstaller to package requests lib properly

The versions of the deis CLI created by "make -C client/ build"
were using PyInstaller 2.1, the current release. This updates
PyInstaller used for packaging to a current SHA, which includes
a hook script for the python requests library to package its
data files correctly.
Merge pull request #2607 from Xe/fix/deisctl/prevent-build-on-windows

fix(deisctl): prevent build on windows
Merge pull request #2618 from Joshua-Anderson/doc_hacking_fix

docs(contrib): Clarify source of DEV_REGISTRY IP Address
Merge pull request #2602 from aledbf/check_discovery-url

feat(vagrant): check if discovery url is defined
style(client): flake8
fix(store): list all monitors in [global] section of config

This is due to a Ceph bug - http://tracker.ceph.com/issues/10012.
Some configuration options aren't read properly if they're not in
the `[global]` section of the Ceph config. This means that the
store-gateway component was only connecting to the initial monitor,
instead of using all the enumerated monitors.

This notation is functionally equivalent, so it'll work just fine
for us.
fix(store-gateway): don't log to stdout

Since we're not execing the radosgw daemon, its view of /dev/stdout
is not really stdout, resulting in the logs being eaten. Now they'll
at least be on the filesystem should debugging be necessary.
Merge pull request #2675 from aledbf/add_wait_to_gateway

fix(gateway): wait until radosgw is accessible