cloud-native-toolkit / cloud-native-toolkit/planning

Split the terraform modules into their own repo

Open
#312 0 comments 0 reactions 0 assignees View on GitHub
Epic
Dominant language
No language data
Stars
4
Forks
1
PR merge metrics
No merged PRs in 30d

Description

We are hitting some challenges with having all the terraform modules in one repository:

- Versioning the whole repository so it is difficult to know which modules have new versions
- Hard to test individual modules during merge
- Does not follow terraform module format
- Difficult to introduce new components
- Hard to enforce standards across the modules
- During `terraform init` stage the same repo is cloned multiple times (takes up space and adds time unnecessarily)

Instead, if the terraform modules were each in their own repository we would address all of these issues. That does mean we will have 30+ new repositories to manage though.

If make this change, I propose we use it as new modules are introduced or when substantial changes are made to existing ones (i.e. slowly phase them out)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.