Infrastructure as Code - Parallel git repo for projects

Description

Infrastructure as Code says that we should version control files necessary to provision and configure infrastructure for a project. Today, you can certainly do that with a separate project, but since many applications have a 1:1 relationship between their code repo and configuration, why not put them in the same project? Create a parallel repo in each project just for infrastructure configuration of that project. Similar to how we have a wiki for each project.

Proposal

Links / references

Documentation blurb

(Write the start of the documentation of this feature here, include:

1. Why should someone use it; what's the underlying problem.
2. What is the solution.
3. How does someone use this

During implementation, this can then be copied and used as a starter for the documentation.)

Open questions

• we can store IaC files together with project files, what is the added benefit of a separate repo?
• what kind of access rights should be around the IaC code, compared to the business code? Can't we solve the same with a single repo and CODEOWNERS?
• could this be used for various IaC needs, like Terraform, Ansible, Kubernetes manifests?
• could we have a repo at the group level, instead of a project for group level IaC management?