+1  one thing here to have in mind as well, is that the "version" field really is just the version of the spec - not the APB itself

an apb-version field would be nice.

that said, IMO there is quite some good room for improvement on additional metadata in that yaml file. For instance, see:
https://github.com/ansibleplaybookbundle/ansible-playbook-bundle/issues/154


On Wed, Jan 24, 2018 at 12:18 PM, Craig Brookes <cbrookes@redhat.com> wrote:
version information would very useful I agree. It is likely something we could define in the metadata for the apb.yaml but to display it, rather than the asb team, I think we would want to add an issue to the https://github.com/openshift/origin-web-catalog

On Wed, Jan 24, 2018 at 10:35 AM, Peter Braun <pbraun@redhat.com> wrote:
It might be worth to suggest that to the Ansible Service Broker team. A workaround could be to add the version to the description in apb.yml (https://github.com/aerogearcatalog/keycloak-apb/blob/master/apb.yml#L3).

Am 24.01.2018 um 11:29 schrieb Jose Miguel Gallas Olmedo <jgallaso@redhat.com>:

Hi,

I think it would be useful to somehow see the version of the APBs from the catalog. Somewhere in this screen maybe:

<Screen Shot 2018-01-24 at 11.19.11.png>

It is very annoying to deploy the whole thing just to see that I don't have the APB I expected.

What do you think?

JOSE MIGUEL GALLAS OLMEDO

ASSOCIATE QE, mobile

M: +34618488633    





--
Craig Brookes
RHMAP 
@maleck13 Github

_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev



--
Matthias Wessendorf

github: https://github.com/matzew 
twitter: http://twitter.com/mwessendorf