terraform-aws-iam-system-user

Removing deprecated ses_smtp_password and adding ses_smtp_password_v4

what

• adding ses_smtp_password_v4

why

• Removing deprecated ses_smtp_password

what

• Tags are now passed along to the underlying aws_iam_user resource
• These tags will apply to the IAM user

why

• The documentation claims tags will be set, and they were previously not.
• Tags are commonly used, both in general AWS and within CloudPosse's modules, so this is important for consistency.

what

• ses_smtp_password added to output

why

• It's convenient to get the ses_smtp_password from module output.

what

• Use the latest label module to support the environment attribute

why

• environment attribute is supported by the latest label module and is useful for naming AWS resources along with namespace, stage and name

what

• Use required_providers to pin Terraform providers

why

• Pinning the module's providers version in required_providers block allows specifying only the required provider version for the module without the need to specify all providers with versions explicitly

what

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

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

terraform-null-label module version bump

what

• Regenerate README.md

why

• Previous version of build-harness has some typos

what

• Add README.yaml

why

• Standardize README

what

• Use splat syntax for outputs to access resources with count

why

• To prevent Terraform warnings:

Warning: output "user_name": must use splat syntax to access aws_iam_user.default attribute "name", because it has "count" set; use aws_iam_user.default.*.name to obtain a list of the attributes across all instances
Warning: output "user_arn": must use splat syntax to access aws_iam_user.default attribute "arn", because it has "count" set; use aws_iam_user.default.*.arn to obtain a list of the attributes across all instances
Warning: output "user_unique_id": must use splat syntax to access aws_iam_user.default attribute "unique_id", because it has "count" set; use aws_iam_user.default.*.unique_id to obtain a list of the attributes across all instances
Warning: output "access_key_id": must use splat syntax to access aws_iam_access_key.default attribute "id", because it has "count" set; use aws_iam_access_key.default.*.id to obtain a list of the attributes across all instances
Warning: output "secret_access_key": must use splat syntax to access aws_iam_access_key.default attribute "secret", because it has "count" set; use aws_iam_access_key.default.*.secret to obtain a list of the attributes across all instances

what

• Fix resources count condition

why

• https://github.com/cloudposse/terraform-null-label.git?ref=tags/0.3.0 works improperly with enabled argument
• string var.enabled is being compared with boolean

What

• Add flag for creation user
• Possibility assign policy
• Add travis
• Update README

Why

• Module can be used in another one, so resources should have the count for skip creation them if aren't necessary.