Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Metadata Plan not returned to cf #49

Closed
ldangeard-orange opened this issue Dec 17, 2018 · 0 comments · Fixed by #51
Closed

Metadata Plan not returned to cf #49

ldangeard-orange opened this issue Dec 17, 2018 · 0 comments · Fixed by #51
Milestone

Comments

@ldangeard-orange
Copy link

ldangeard-orange commented Dec 17, 2018

We describe plan in coab-depls/cf-apps-deployments/coa-<produit>-broker/template/coa-<produit>-broker_manifest-tpl.yml with metadata, for exemple

CATALOG_YML: |
          servicebroker:
            catalog:
              services:
              - id: cf-mysql-ondemand-service
                name: cf-mysql-ondemand
                description: "MariaDB databases on demand on dedicated Galera cluster "
                bindable: true
                plans:
                  - id: plan-coab-mariadb-small
                    name: small
                    description: Dedicated MariaDB Galera Cluster 2GB data storage with 4GB RAM/1CPU
                    free: false
                    metadata:
                      bullets:
                      - 2GB storage
                      - 50 concurrent connections
                      costs:
                      - amount:
                          eur: 48.0
                        unit: Monthly
                      displayName: Small Data 2GB - 4GB RAM/1CPU

We need to send this metadata to cf marketplace.
List of fields : https://github.com/openservicebrokerapi/servicebroker/blob/master/profile.md#plan-metadata-fields

@gberche-orange gberche-orange changed the title Metadata Plan not send to cf Metadata Plan not returned to cf Mar 12, 2019
@gberche-orange gberche-orange added this to the 0.28.0 milestone May 16, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants