Using kitchen-terrform to set up extra context

Question

I'm using kitchen-terraform in order to verify a terraform module I'm building. The module is a part of a larger infra. It's dependent on some of the network being available. where later it's used to spin more servers etc.

I just want to know if there's a way in kitchen-terraform to create some pieces of infra before the module is tested.

In my case it's creating a new VPC with some connections and with existing PVC, security groups and subnets. I want to verify that the peering connections were established correctly as well as spin up some ec2 instances to verify the status of the network.

Answer 1

Use .kitchen.yml file which cans specify where the terraform code exists to execute:

provisioner:
  name: terraform
  directory: path/to/terraform/code
  variable_files:
   - path/to/terraform/variables.tfvars

Create a main.tf in the test location which will buld all the infrastucture you want. the order of execution should be controlled by the dependencies of the resources.

Taking that your testing is in the same repository as your module, do something like this:

├── .kitchen.yml
├── Gemfile
├── Gemfile.lock
├── README.md
├── terraform
│   ├── my_module
│       ├── main.tf
│       └── variables.tf
├── test
    ├── main.tf
    └── terraform.tfvars

the .kitchen.yml file should look something like this:

provisioner:
  name: terraform
  directory: test
  variable_files:
   - test/variables.tfvars
  variables:
    access_key: <%= ENV['AWS_ACCESS_KEY_ID'] %>
    secret_key: <%= ENV['AWS_SECRET_ACCESS_KEY'] %>

Your test/main.tf will create the module with any other test code you want:

provider "aws" {
  access_key = "${var.access_key}"
  secret_key = "${var.secret_key}"
  region = "${var.region}"
}

...

module "my_module" {
  name = "foo"
  source = "../terraform/my_module"
...
}

resource "aws_instance" "test_instance_1" {
...
}