Adding automation script to update version in Community Catalog

[cniackz]

There is a catalog in:

https://github.com/k8s-operatorhub/community-operators

And we have a script to update the MinIO Operator Version that I would like to add so other engineers can update the version if needed.

[harshavardhana]

Not sure what this is and why this script has permissions to push to the origin and create new branches - can you explain what this does?

[cniackz]

@harshavardhana

Overview, the idea is to update the Operator version in Community Catalog.

Steps are as follow:

1. I get a fresh copy of both repos: Operator and Community repo.
2. Then I make sure they are updated so same commits are observed in my forked repos and official repos.
3. I execute the olm scripts so that I get the bundle, needed for Operator installation in k8s environment.
4. I create the branch in the community repo, so that we can have a PR for the update as other companies do.
5. Then I copy all needed files for Operator Lifecycle Manager to be able to install this new version on a cluster.
6. And finally I send the PR for review and if all tests are passing, they will merge it and we are going to be up to date.

Added more explanation on how I use this script to update community catalog.