terraform-aws-key-pair

what

• Update aws provider to >= 2.0 avoid module version conflicts when used with >= 3.0 modules (eg. aws-eks-node-group).

why

• This module is being used with terraform-aws-eks-node-group which needs aws provider version to be >= 3.0 which is causing version conflicts.

references

• See cloudposse/terraform-aws-eks-node-group#41 for details. This tackles one of the modules causing the issue.

what

• Add tags population to aws_key_pair that are already using the variable

why

• For billing to be able to filter resources by tag
• Requirements within a company to tag all resources that support tags

what

• Delay filename outputs until files exist

what

• Instead of running an external command, use terraform's built in way of setting permissions on local file resources

why

• using native way always better

what

• Add a private_key to output parameters

why

• Sometimes it's useful to have this available -- e.g. for CI situations in which one needs to create a scratch key, create an instance, then provision the instance using the newly-created keypair.

what

• Do not show private key content

why

• Avoid showing private key in terraform diffs

what

• Use the latest label module to support the environment attribute

why

• The environment attribute is useful for naming AWS resources

what

• Bump terraform-null-label to 0.16.0

why

• Stay up to date

what

• Port module to Terraform 0.12
• Pin all providers
• Add example for testing
• Add bats and terratest tests for the example
• Add Codefresh badge to point to the test pipeline in terraform-modules project
• Update README

why

• Module currently does not work with 0.12. Much easier syntax
• Better regression control
• Automatically test the example on every commit and pull request
• Provision resources on AWS in the test account and check the outputs for the correct values
• terraform-modules project contains pipelines for all terraform modules

what

• Fix key_filename logic

why

• If generate_ssh_key is false, line 19 fails because public_key_filename has not been set. This always sets local vars and allows value of generate_ssh_key to determine usage

what

• Add trigger for local-exec

why

• The chmod resource was not triggering when it should

what

• Regenerate README.md

why

• Previous version of build-harness has some typos