No, sadly (from a cost to run bosh perspective)

It's not necessary to change tag to recreate a final release or upload it. The cf-212.yml is permanent in the repo (unless someone removes it) and can be used from any commit. You will want to change

Nice find. wrote:

The first dozen lines of [2] show that you're deploying a bosh via bosh-init (which I'll call a microbosh). wrote:

Josh, to confirm - is uploading other bosh releases to your microbosh also failing? Eg uploading releases from bosh.io? wrote:

Errands run their script on a new VM

I don't think there is anything in bosh to get this done - Perhaps look at including consul agent and using consul exec? Or perhaps ansible? <michael.grifalconi(a)studenti.unimi.it> wrote:

Perhaps look at gogobosh which is a golang client for much of the API <viniciusccarvalho(a)gmail.com> wrote:

There are two issues - the second is that bosh-bootstrap uses a project "cyoi" (choose your own infrastructure) and underneath it uses "fog" - its quite possible that either or both do not yet support

Try this idea https://github.com/concourse/concourse/blob/master/manifests/bosh-lite.yml#L4 wrote:

If you use a normal (non-light) stemcell then `bosh micro deploy` will create a private AMI for you. You will need to be in an AWS China VM, a jumpbox/bastion/work VM. Use one of these stemcells - htt

Congrats BOSH team! I'll upgrade my little tutorial repos to use new GitHub releases asap. wrote:

I think "bosh public stemcells" is deprecated in lieu of bosh.io. I think. wrote:

http://bosh.io/releases/github.com/cloudfoundry-incubator/bosh-openstack-cpi-release is the OpenStack CPI It should work like the AWS one if you have original flat networking. If you have neutron the

Testing testing 10.1.2.3.