Is your feature request related to a problem? Please describe.
In order to install an operator with a specific version and sequentially test upgrades on that particular operator we need at first to discover what versions are available on a given catalog for that operator. That list will also serve to inform operator developers wanting to troubleshoot their operators and operator bundles.
Describe the solution you'd like.
A new command and sub command on opcap bundle list would take catalogs, channels and also package name if necessary to list all the bundles and consequentially all the versions available for that specific operator. That can be done by using the operator registry api github.com/operator-framework/operator-registry/pkg/client
Describe alternatives you've considered.
I considered using the OLM clientset api but no information about specific bundles are provided. We can supposedly try the same with just the currentCSV fields on the package/channel combination to create new subscriptions for that startingCSV. That's not simple though. We need to understand all the CSV semantic names to put them in order and try upgrades on that.
Is your feature request related to a problem? Please describe.
In order to install an operator with a specific version and sequentially test upgrades on that particular operator we need at first to discover what versions are available on a given catalog for that operator. That list will also serve to inform operator developers wanting to troubleshoot their operators and operator bundles.
Describe the solution you'd like.
A new command and sub command on opcap
bundle listwould take catalogs, channels and also package name if necessary to list all the bundles and consequentially all the versions available for that specific operator. That can be done by using the operator registry api github.com/operator-framework/operator-registry/pkg/clientDescribe alternatives you've considered.
I considered using the OLM clientset api but no information about specific bundles are provided. We can supposedly try the same with just the currentCSV fields on the package/channel combination to create new subscriptions for that startingCSV. That's not simple though. We need to understand all the CSV semantic names to put them in order and try upgrades on that.
Steps to make this feature available: