Remove `opm registry serve`

[joelanford]

The sqlite-based commands in opm have been deprecated for almost two years. We know of some users still building sqlite-based catalogs, but they are also converting them to FBC and serving FBC.

I propose that we remove the opm registry serve command so that we can avoid concerns around maintaining parity between the sqlite server (which is not receiving new features) and the FBC server (which is receiving new features).

[Jamstah]

Notes from Tue 6th June operator framework meeting (see recording for more detail):

Suggest to remove because it is diverging and has additional maintenance cost.

Consumers who have not migrated to FBC could use the old OPM image for serving catalogs.

It is easy to migrate an sqlite database to FBC to enable serving.

Could we enable automatic migration and then just run the FBC serve? (concerns about implying that its ok for people to still use sqlite)

Need to look more closely at the index commands, which make assumptions that there is an opm registry serve command.

Note: If we are following semver, We'll need to rev the major version to 2.0.0

[Jamstah]

I did a quick experiment not long ago to see how much size I could take out of a catalog image by building just the FBC serve command from opm: https://github.com/jamstah/operator-registry/tree/opm-serve.

It struck me that this could be a carrot for getting users to migrate to FBC in their catalogs - add an option for a smaller image but only if they use FBC.

Might be overcomplicating things, but thought I'd share.

-rwxr-xr-x.  1 jammy jammy 73178008 May 30 10:17 opm
-rwxr-xr-x.  1 jammy jammy 25223168 Jun  8 09:28 opm-serve

[github-actions[bot]]

Issues go stale after 90 days of inactivity. If there is no further activity, the issue will be closed in another 30 days.

[github-actions[bot]]

This issue has been closed due to inactivity.