Support online stemcell #128
Assignees
Labels
Comments
|
to reduce prerequisite for #108 , we need this feature. A workaround is to reuse the bosh.io AWS S3 bucket |
Merged
o-orand
added a commit
that referenced
this issue
Jul 13, 2018
By default, we use offline stemcell, but it can be overridden by `shared-config.yml` or `private-config.yml` closes #128
o-orand
added a commit
that referenced
this issue
Jul 13, 2018
By default, we use offline stemcell, but it can be overridden by `shared-config.yml` or `private-config.yml`. We also rename `bosh-stemcell` resource to `((stemcell-main-name))` to be clearer. closes #128
o-orand
added a commit
that referenced
this issue
Jul 13, 2018
By default, we use offline stemcell, but it can be overridden by `shared-config.yml` or `private-config.yml`. We also rename `bosh-stemcell` resource to `((stemcell-main-name))` to be clearer. closes #128
o-orand
added a commit
that referenced
this issue
Jul 13, 2018
By default, we use offline stemcell, but it can be overridden by `shared-config.yml` or `private-config.yml`. We also rename `bosh-stemcell` resource to `((stemcell-main-name))` to be clearer. closes #128
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We moved from online stemcell support (ie bosh.io) to S3, but during bootstrap it could be nice to be able to get stemcell directly from bosh.io. We already have this support for bosh release.
Leverage property in
shared-config.yml/private-config.ymlThe text was updated successfully, but these errors were encountered: