Writing a Terraform Module: Difference between revisions

From NovaOrdis Knowledge Base
Jump to navigation Jump to search
Line 26: Line 26:
* README or README.md. Should contain a description of the module. Examples can be included in an example directory.
* README or README.md. Should contain a description of the module. Examples can be included in an example directory.
* LICENSE
* LICENSE
* Recommended file names:
* Recommended file (they should exist even if they are empty):
** <code>main.tf</code>
** <code>main.tf</code>
** <code>variables.tf</code>
** <code>variables.tf</code>
** <code>outputs.tf</code>
** <code>outputs.tf</code>
* For a complex module, resource creation may be split into multiple files, but '''any nested module calls should be in the main file'''.

Revision as of 01:41, 14 November 2019

External

Internal

Reference Example

Playground

https://github.com/ovidiuf/playground/tree/master/hashicorp/terraform/blue-module

Procedure

To define a module, create a new root directory for it and place one or more .tf files inside it.

Standard Structure

Everything is optional, except for the root module:

  • Root module - this is the only required element for the standard module structure, and it consists in .tf files - which must exist - in the root directory of the module.
  • README or README.md. Should contain a description of the module. Examples can be included in an example directory.
  • LICENSE
  • Recommended file (they should exist even if they are empty):
    • main.tf
    • variables.tf
    • outputs.tf
  • For a complex module, resource creation may be split into multiple files, but any nested module calls should be in the main file.