We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi,
I have a lot to learn; so may ask stupid questions.
I developed an Operator with the SDK and use opm to generate a Catalog; using opm index ...
opm
opm index ...
I read SQLLite Catalogs are dead/dieing/deprecated and File Based Catalogs their replacement.
I see opm has a migrate command to move from SQLLite to FBC; but can I generate a FBC from the outset?
migrate
I've looked around and cannot find much information.
Sorry to ask.
The text was updated successfully, but these errors were encountered:
Well there's a bit of doc here for opm init:
opm init
https://olm.operatorframework.io/docs/reference/file-based-catalogs/
But I feel like we must have a bunch more somewhere? @grokspawn
Sorry, something went wrong.
This is probably the best resource right now: https://olm.operatorframework.io/docs/tasks/creating-a-catalog/#creating-a-catalog
No branches or pull requests
Hi,
I have a lot to learn; so may ask stupid questions.
I developed an Operator with the SDK and use
opm
to generate a Catalog; usingopm index ...
I read SQLLite Catalogs are dead/dieing/deprecated and File Based Catalogs their replacement.
I see
opm
has amigrate
command to move from SQLLite to FBC; but can I generate a FBC from the outset?I've looked around and cannot find much information.
Sorry to ask.
The text was updated successfully, but these errors were encountered: