Hi Dmitriy,

Are you still planning to propose a config/final.yml with metadata that
bosh.io could render ? Should we instead continue this over the bosh-notes
repo ?

Thanks in advance,

Guillaume.

On Sat, Jul 18, 2015 at 3:39 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

I am thinking we can add metadata to config/final.yml (and eventually
include it in the release tarballs in release.MF). Once config/final.yml
includes metadata, bosh.io can pull it in down and include it on release
versions pages.

I'll reply to this thread with a format for config/final.yml based on your
repo in coming days.

Thanks for kicking this off!

On Fri, Jul 10, 2015 at 2:23 AM, Guillaume Berche <bercheg(a)gmail.com>
wrote:

Hi,

I'm wondering whether there are plans to add meta-data to bosh release
manifest, as to support better discoverability of bosh releases.

The bosh hub is providing a great one shop place to find bosh releases,
and it would be great to have it augmented with meta-data / classification.

This meta-data could be external to the release (e.g. in bosh-hub) or
embedded in the release similar to juju charms meta-data [1] or most
package manager provide (yum, apt ...) to attach meta-data to packages.

I drafted possible meta-data / classification into [2] as to start the
discussion.

Thanks in advance,

Guillaume.

[1] https://jujucharms.com/docs/stable/authors-charm-metadata
[2] https://github.com/cloudfoundry-community/awesome-bosh-releases

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh