v0.20.0

feat(aws-key-pair): enable the ssm parameter store to record the key-pair distribution @haidargit (#77)

what

In this PR, we can use the AWS SSM Parameter store resource to facilitate the secure management of private key information. This resource allows us to gather the private key information generated by the current module and securely store it in the parameter store.

why

The objective behind this enhancement is to ensure the secure distribution of private key ownership within the AWS infrastructure. We can centrally manage and protect sensitive information, increasing operational efficiency and reducing the likelihood of unauthorized access to critical resources.

references

No issue relates to current improvement.

I have run these required commands,
make init
make readme

Kindly review this PR for module improvements. Thank you

v0.19.0

Support AWS Provider V5 @max-lobur (#75)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Sync github @max-lobur (#73)

Rebuild github dir from the template

git.io->cloudposse.tools update @dylanbannon (#70)

what and why

Change all references to git.io/build-harness into cloudposse.tools/build-harness, since git.io redirects will stop working on April 29th, 2022.

References

• DEV-143

v0.18.3

🚀 Enhancements

Update to get rid of sensitive file warning from terraform @brunzefb (#69)

what

• Updated to local_sensitive_file resource, changed provider versions.

why

• This removes a terraform warning

v0.18.2

🤖 Automatic Updates

Update context.tf @cloudpossebot (#66)

what

This is an auto-generated PR that updates the context.tf file to the latest version from cloudposse/terraform-null-label

why

To support all the features of the context interface.

v0.18.1

🚀 Enhancements

Fix: module enablement; Import Key Test @korenyoni (#65)

what

• Ensure module adheres var.enabled
• fix tests and ensure examples_import_key_test is run in test suite

why

• Resources were created even when var.enabled was false

references

• Issue identified in cloudposse/terraform-aws-components#340

🐛 Bug Fixes

Fix: module enablement; Import Key Test @korenyoni (#65)

what

• Ensure module adheres var.enabled
• fix tests and ensure examples_import_key_test is run in test suite

why

• Resources were created even when var.enabled was false

references

• Issue identified in cloudposse/terraform-aws-components#340

v0.18.0

context.tf updated to v0.24.1, minimum required Terraform version bumped to 0.13.0 when needed, readme updated @maximmi (#60)

what

• update context.tf to v0.24.1
• minimum required Terraform version bumped to 0.13.0
• readme updated, Bridgecrew compliance badges added

why

• It allows for setting the letter case of tag names and labels, back compatibility with context v0.22.0 and below
• we have dropped support for Terraform 0.12
• To be able see and fix the recommendations from Bridgecrew so we can position our modules as standards compliant

Closes #62
Closes #63

v0.17.0

Terraform 0.14 upgrade @maximmi (#58)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

0.16.1: Configure Renovate (#54)

Co-authored-by: Renovate Bot <[email protected]>

0.16.0: Convert to context (#52)

Co-authored-by: Frank Klaassen <[email protected]>
Co-authored-by: actions-bot <[email protected]>

0.15.0 update aws provider version

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.