manage github/canopybmc via opentofu - #1
sinuscosinustan wants to merge 1 commit into
Conversation
mynetz
left a comment
mynetz
left a comment
There was a problem hiding this comment.
I reviewed what I perceive as the content (the labels).
The TF code itself largely depends on how this is supposed to work later. Which brings me to my main point: I think reviewing it will require a prior discussion on how this is supposed to work.
We should have an issue or the PR description on what this "code" should archive. That said, this PR serves the discussion very well as a starting point.
Provision and standardise the organisation's GitHub repositories, labels
and teams from code instead of clicking through the web UI or via the
API.
This way, we can ensure that our settings match with our expectations,
and avoid misconfiguration from manual changes.
The required labels will be automatically created based on a list, which
might get handy after a release.
Create a github-repository module that creates the repository, manages
all the settings, issue labels and rulesets. The existing repostiories
were imported via `tofu import`.
The state will be locally stored for now, but later on stored either in
GCS or any other central place.
Anything in this repository must be approved by the Canopy Management
team.
Assisted-by: claude:claude-opus-5 [Tofu variables]
Assisted-by: zickzack:kolle-mate [CI, Label and repo settings,
review claude output]
Signed-off-by: Tan Siewert <tan.siewert@9elements.com>
|
I like it to have otherwise possibly erratic settings to have cleanly documented and reproducible. Do you checked with the infrastructure team how they handle it? Or if they have similar plans? Just to avoid duplicate work (in terms of chosen framework and alike) On the configuration or settings itself I can't really comment, as I'm not to much into it. That said there's also nothing catching my eye here. |
3 participants
Note
None of this has been deployed yet (e.g. labels and such). The changes will be deployed after the PR got merged, since we have quite a few changes in here. A diff result from
tofu planwill be available as GitHub Gist (contact me via chat for it) due to the length at the bottom of the PR description.Provision and standardise the organisation's GitHub repositories, labels and teams from code instead of clicking through the web UI or via the API.
This way, we can ensure that our settings match with our expectations, and avoid misconfiguration from manual changes. The required labels will be automatically created based on a list, which might get handy after a release.
Create a github-repository module that creates the repository, manages all the settings, issue labels and rulesets. The existing repostiories were imported via
tofu import.The state will be locally stored for now, but later on stored either in GCS or any other central place.
Anything in this repository must be approved by the Canopy Management team.
Assisted-by: claude:claude-opus-5 [Tofu variables]
Assisted-by: zickzack:kolle-mate [CI, Label and repo settings, review claude output]