Seth Vargo 93b9047472 Update website whitespace and formatting

2015-04-22 19:47:11 -04:00

3.5 KiB

Raw Blame History

layout	page_title	sidebar_current	description
docs	Using Modules	docs-modules-usage	Using modules in Vault is very similar to defining resources.

Module Usage

Using modules in Vault is very similar to defining resources:

module "consul" {
  source = "github.com/hashicorp/consul/vault/aws"
  servers = 3
}

You can view the full documentation for the syntax of configuring modules here.

As you can see, it is very similar to defining resources, with the exception that we don't specify a type, and just a name. This name can be used elsewhere in the configuration to reference the module and its variables.

The existence of the above configuration will tell Vault to create the resources in the "consul" module which can be found on GitHub with the given URL. Just like a resource, the module configuration can be deleted to remove the module.

Source

The only required configuration key is the source parameter. The value of this tells Vault where the module can be downloaded, updated, etc. Vault comes with support for a variety of module sources. These are documented on a separate page.

Prior to running any command such as plan with a configuration that uses modules, you'll have to get the modules. This is done using the get command.

$ vault get
...

This command will download the modules if they haven't been already. By default, the command will not check for updates, so it is safe (and fast) to run multiple times. You can use the -u flag to check and download updates.

Configuration

The parameters used to configure modules, such as the servers parameter above, map directly to variables within the module itself. Therefore, you can quickly discover all the configuration for a module by inspecting the source of it very easily.

Additionally, because these map directly to variables, they're always simple key/value pairs. Modules can't have complex variable inputs.

Outputs

Modules can also specify their own outputs. These outputs can be referenced in other places in your configuration. For example:

resource "aws_instance" "client" {
  ami = "ami-123456"
  instance_type = "m1.small"
  availability_zone = "${module.consul.server_availability_zone}"
}

This purposely is very similar to accessing resource attributes. But instead of mapping to a resource, the variable in this case maps to an output of a module.

Just like resources, this will create a dependency from the aws_instance.client resource to the module, so the module will be built first.

Plans and Graphs

With modules, commands such as the plan command and graph command will show the module as a single unit by default. You can use the -module-depth parameter to expand this graph further.

For example, with a configuration similar to what we've built above, here is what the graph output looks like by default:

![Vault Module Graph](docs/module_graph.png)

But if we set -module-depth=-1, the graph will look like this:

![Vault Expanded Module Graph](docs/module_graph_expand.png)

Other commands work similarly with modules. Note that the -module-depth flag is purely a formatting flag; it doesn't affect what modules are created or not.

3.5 KiB Raw Blame History