Automate managing settings across all charmed kubeflow repositories

ca-scribner commented 8 months ago

Context

Charmed Kubeflow and its rocks totals ~30-40 github repositories. The settings for these are currently managed manually, meaning if we decide to change something like branch protection rules then an engineer must manually change it everywhere.

Proposed here is that we automate this. Options include:

using the same tooling that the observability team uses
using terraform as demo'd in the lightning talks from the Riga sprint (see Tuesday morning's presentations)

This should at least include all settings discussed in this github repo settings spec, as well as manage the labels available in every repo. This ideally should be executed via CI in either the bundle or kubeflow-ci repo. Discovery of repos could be done using the topics we set for our repos.

What needs to get done

automate github repo settings management
use it to sync the settings for all repos

Definition of Done

all charmed kubeflow repos have consistent github repo settings

syncronize-issues-to-jira[bot] commented 8 months ago

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5291.

This message was autogenerated

ca-scribner commented 7 months ago

This is similar to but different from canonical/kubeflow-ci#127:

canonical/bundle-kubeflow#811 (here) proposes we automate the github repository settings
canonical/kubeflow-ci#127 proposes we detect divergence in the content of the repo.

rgildein commented 3 months ago

Maybe we can use similar approach as SolEng team used here. They are using Terraform to set repos.

canonical / bundle-kubeflow