-
Notifications
You must be signed in to change notification settings - Fork 33
[code-infra] IaC for our GitHub org #1235
Copy link
Copy link
Open
Labels
priority: lowTo delay as much as possible.To delay as much as possible.scope: code-infraInvolves the code-infra product (https://www.notion.so/mui-org/5562c14178aa42af97bc1fa5114000cd).Involves the code-infra product (https://www.notion.so/mui-org/5562c14178aa42af97bc1fa5114000cd).type: new featureExpand the scope of the product to solve a new problem.Expand the scope of the product to solve a new problem.
Metadata
Metadata
Assignees
Labels
priority: lowTo delay as much as possible.To delay as much as possible.scope: code-infraInvolves the code-infra product (https://www.notion.so/mui-org/5562c14178aa42af97bc1fa5114000cd).Involves the code-infra product (https://www.notion.so/mui-org/5562c14178aa42af97bc1fa5114000cd).type: new featureExpand the scope of the product to solve a new problem.Expand the scope of the product to solve a new problem.
Summary:
See https://mui-org.notion.site/Configuration-of-the-repositories-306cbfe7b6608047ba91e4c7a7bff846
We have the intention to sync settings between repositories, but the sync is only performed during repository creation. There is no enforcement or automation for our repo configuration. Moreover creating a new repository and going through this guide is cumbersome.
Solution:
Introduce terraform and their github provider and treat our GH org infra as code. We encode the "gold standard" in a terraform module and define all our repositories from this gold standard. New repository creation will be as much as adding another entry, and syncing a settings change will be instant, no bifurcation possible.
We can also use the netlify provider for our netlify setup
Adjacent