You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@matzew it's an interesting idea. Do you want to add a licence field because an apb could have a difference licence? Do you mind explaining in more detail how this can be used?
I, as a customer 😄, should be able to specify the license of my -apb container, in the metadata. I'd compare this a bit w/ package.json or pom.xml, where you also have option to define the license of your project.
Also, wouldn't it be interesting to see, in the catalog, if the service (and the apb) are under license XYZ?
In middleware (Red Hat) we recently added LICENSE.XML to a bunch of projects, that list all licenses of their dependencies. So if your offering (e.g. feedhenry/mcp-standalone), has a "dependency" to a bunch of APBs, we could use that metadata also to list the license of the -apb.
It would be nice if the
apb.yaml
would support (and being valid) alicense:
field, so that one could do:The text was updated successfully, but these errors were encountered: