v1.3.0

• No changes

v1.2.0

4.x version @Benbentwo (#21)

what

• Updates to 4.X

why

• Latest TLS Provider

references

• #20

v1.1.0

Version Lock 3.X @Benbentwo (#20)

what

• Lock version to 3.X

why

• Version 4.0 came out with release notes:

resource/tls_cert_request: Attribute key_algorithm is now read-only, as it's inferred from private_key_pem

Note:

This is a bandaid fix, ideally we should upgrade to 4.X, this will take time to upgrade many other components however, since many breaking changes we're introduced I'm proposing a version lock until that time

v1.0.0 Remove deprecated inputs

Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules.

Remove key algorithm from tls_cert_request and tls_locally_signed_cert @nitrocode (#14)

what

• Remove key_algorithm from tls_cert_request
• Remove ca_key_algorithm from tls_locally_signed_cert

why

• Deprecated

references

• Closes #13
• https://registry.terraform.io/providers/hashicorp/tls/latest/docs
• https://registry.terraform.io/providers/hashicorp/tls/latest/docs/resources/cert_request#key_algorithm

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

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.5.0

🐛 Bug Fixes

Fix: Use `module.this.id` Instead of `module.this.name` @nitrocode (#10)

what

• Use context id instead of name

why

• Keep the keys unique

references

• Could be utilized by cloudposse/terraform-aws-ec2-client-vpn#24

v0.4.0

feat(locally_signed): Adding locally signed option @r351574nc3 (#7)

what

• Feature flag for locally signed certificates

why

• Locally signed certificates allow the use of existing CA certificate to be used to create a new cert. This is something that can't normally be done with self-signe certificates

references

• fixes cloudposse/terraform-aws-ec2-client-vpn#6

v0.3.0

Add support for importing self-signed certificate to ACM @r351574nc3 (#5)

what

• ACM support allows using aws_acm_certificate TF resource to store certificates and keys directly in ACM for use with other AWS services that access certificates in that way.

why

• Support the following use case: VPN client uses self-signed-cert to create VPN endpoints using certificate based authentication and storing certificates in ACM

references

• N/A

v0.2.1

🤖 Automatic Updates

Update context.tf @cloudpossebot (#4)

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.2.0

🚀 Enhancements

Feat: Allow Certificate and Private Key Extensions to be Overridden @korenyoni (#3)

what

• Allow certificate and private key extensions to be overridden.
• Add test for extension override.
• Fix order of variables in assert.Equal in test suite.

why

• Some use cases require that extensions other than .pem and .key be used for the certificate and private key.

references

• N/A

Initial release

This is the initial release for ssm-tls-self-signed-cert, which provides creation and writing of a self signed certificate to SSM or ASM.