Problem:

Every time there is a change required on the libraries that samples operator deploys and manages we need to communicate with the library providers to request changes. One example of such change includes the new requirement in OCP 4.11 to include the group on the apiVersion of each Template and Image Stream resource. The process to communicate today is manual.

Goal:

Make it easy to communicate with Issue creation on each of the root repositories for each library.

Why is it important?

There is a lot of libraries and communicating with the owners is not automated. Adding automation for this will simplify our support of Samples Operator.

Use cases

As a sample developer I will like to have a fast and easy way to send messages to all the library owners when we need to notify them of a required change.

Acceptance criteria

I can run a job that can create issues with the notification and call for action right on each repository that hold the root of the library

Dependencies (External/Internal)

Each repository would have to be accessible publicly so that we can use github APIs

Design Artifacts

One way to accomplish this is to create a gihub workflow that will use the gihub apis to make calls to create issues in library root repos. This is an example we use in helm certification: https://github.com/openshift-helm-charts/charts/blob/main/.github/workflows/test.yml

Exploration

Note

We should be able to get the repo list from here: https://github.com/openshift/library/blob/master/official.yaml