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
While we wait for operator-framework/catalogd#139, I propose that we start using catalogd's CatalogMetadata API instead of its BundleMetadata and Package APIs.
The CatalogMetadata API contains (almost) all of the FBC that the eventual catalogd file server will, so it is a good step forward, and is something that folks implementing some of the existing RFCs can use right now. This will ease an eventual migration to the catalogd file server.
Catalogd main branch currently has CatalogMetadata APIs enabled. We just need to ask catalogd maintainers to cut a release and bump our dependency on it.
The text was updated successfully, but these errors were encountered:
joelanford
changed the title
Move variable sources and/or entity sources over to CatalogMetadata
Make catalogd's CatalogMetadata APIs available for operator-controller
Aug 15, 2023
Sorry, I misunderstood it at first. This ticket only aims at making CatalogMetadata available to operator-controller which was already done in #339 / #336.
While we wait for operator-framework/catalogd#139, I propose that we start using catalogd's
CatalogMetadata
API instead of itsBundleMetadata
andPackage
APIs.The
CatalogMetadata
API contains (almost) all of the FBC that the eventual catalogd file server will, so it is a good step forward, and is something that folks implementing some of the existing RFCs can use right now. This will ease an eventual migration to the catalogd file server.Catalogd
main
branch currently hasCatalogMetadata
APIs enabled. We just need to ask catalogd maintainers to cut a release and bump our dependency on it.The text was updated successfully, but these errors were encountered: