Background
The EP originally added olm.gvk.provided for two reasons:
To make it easier to distinguish provided vs required GVKs (the existing olm.gvk property is ambiguous by itself)
To keep 100% backward-compatibility for the GRPC API. The olm.gvk property lacks a plural field, but the GRPC api.Bundle's provided APIs field contains a plural field that is populated when an sqlite DB is served.
Description
This EP update removes olm.gvk.provided and clarifies handling of plural fields.
By adding the olm.gvk.required property there is now at least an implicit disambiguation between olm.gvk and olm.gvk.required.
Background The EP originally added
olm.gvk.provided
for two reasons:olm.gvk
property is ambiguous by itself)olm.gvk
property lacks aplural
field, but the GRPCapi.Bundle
's provided APIs field contains a plural field that is populated when an sqlite DB is served.Description This EP update removes
olm.gvk.provided
and clarifies handling ofplural
fields.olm.gvk.required
property there is now at least an implicit disambiguation betweenolm.gvk
andolm.gvk.required
.Signed-off-by: Joe Lanford joe.lanford@gmail.com