ADR 3: Manage Terraform modules

0003-manage-terraform-modules.md

ADR 3: Manage Terraform modules

• Status: proposed
• Deciders: [list everyone involved in the decision]
• Date: 2019-02-09

Technical Story: n/a

Context and Problem Statement

Non-root Terraform modules should be reusable. They should also be easy to version. Let's decide on a module organization scheme, and get some experience with it. Based on what we learn from use, we may supersede this ADR. If it needs refinement, then so be it.

Decision Drivers

• [driver 1, e.g., a force, facing concern, …]
• [driver 2, e.g., a force, facing concern, …]
• …

Considered Options

• [option 1]
• [option 2]
• [option 3]
• …

Decision Outcome

Chosen option: "[option 1]", because [justification. e.g., only option, which meets k.o. criterion decision driver | which resolves force | … | comes out best (see below)].

Positive Consequences

• [e.g., improvement of quality attribute satisfaction, follow-up decisions required, …]
• …

Negative Consequences

• [e.g., compromising quality attribute, follow-up decisions required, …]
• …

Pros and Cons of the Options

[option 1]

[example | description | pointer to more information | …]

• Good, because [argument a]
• Good, because [argument b]
• Bad, because [argument c]
• …

[option 2]

[example | description | pointer to more information | …]

• Good, because [argument a]
• Good, because [argument b]
• Bad, because [argument c]
• …

[option 3]

[example | description | pointer to more information | …]

• Good, because [argument a]
• Good, because [argument b]
• Bad, because [argument c]
• …

Links

• [Link type] [Link to ADR]
• …