v0.13.0

chore: add overwrite argument back @gberenice (#53)

what

• Unfortunately, we have to add the overwrite argument back due to the confusion of its deprecation:

Lastly, and unfortunately, configurations expecting the standard update flow will need to keep overwrite = true set until this becomes the default behavior in v6.0.0. Removing it in v5.X will result in the default value of false, preventing the parameter value from being updated, causing persistent differences.

why

• Prevent undesired behaviour.

references

• hashicorp/terraform-provider-aws#25636 (comment)

v0.12.0

chore: remove deprecated `overwrite` argument @meysam81 (#52)

fixes #51

Sync github @max-lobur (#48)

Rebuild github dir from the template

v0.11.0

• No changes

v0.10.0

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

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

🚀 Enhancements

update outputs to work with ignore_value_changes ssm parameters @1david5 (#41)

what

• Update outputs to include the name and values of the ignore_value_changes parameters.

why

• Output arguments for the ignore_value_changes resource

v0.9.0

Parameters that can be modified by another tool @1david5 (#40)

what

• Add an alternative parameter resource with a lifecycle that ignores value changes.
• Also add the new data_type argument to the aws_ssm_parameter resource.

why

• Allow the user to create parameters that can be modified by another tool in the future without affecting terraform apply, preventing errors like this:
  

v0.8.5

🚀 Enhancements

Change default param type from SecretString to SecureString. @MattCWheeler (#39)

Change default parameter type from SecretString to SecureString.

SecretString is a term from AWS Secrets Manager, and is not valid with SSM Parameter Store. The corresponding type is "SecureString".

v0.8.4

🚀 Enhancements

Use context for tags @nitrocode (#38)

what

• Use context for tags

why

• Fixes an issue if only context is passed in, it won't tag it unless var.tags is also passed in. This change will use context if it's available.

references

N/A

v0.8.3

🚀 Enhancements

feat: Template provider removed from versions.tf @DovnarAlexander (#36)

what

• Template provider removed from versions.tf

why

• This provider is not used and deprecated. On ARM platforms Terraform raises an exception (because it does not have a build for it)

references

• https://registry.terraform.io/providers/hashicorp/template/latest/docs

v0.8.2

🚀 Enhancements

Fix: `var.enabled` for Parameter Read, Testing Suite Overhaul @korenyoni (#33)

what

• Fix var.parameter_read not honoring var.enabled.
• Overhaul tests to properly test for map output.
• Overhaul tests to have a parallel test for a disabled context.
• Test that module outputs work as expected in both enabled and disabled contexts.
• Misc: Fix README snippets.
• Misc: Bump module in examples/complete.

why

• This module will still read from SSM Parameter Store even if var.enabled is false.
• Tests are not sufficient to test for the use case described above.
• Tests do not properly test map output.
• Misc: README is out of date (git source instead of Terraform registry).

references

• N/A