v0.37.0

feat: Add tags to `aws_appautoscaling_target` @MaxymVlasov (#133)

what

Update terraform-aws-dynamodb-autoscaler module to set tags for aws_appautoscaling_target resources

references

Related PR: cloudposse/terraform-aws-dynamodb-autoscaler#65

🤖 Automatic Updates

Update .github/settings.yml @osterman (#132)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update release workflow to allow pull-requests: write @osterman (#131)

## what - Update workflow (`.github/workflows/release.yaml`) to have permission to comment on PR

why

• So we can support commenting on PRs with a link to the release

Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#130)

## what - Update workflows (`.github/workflows`) to use shared workflows from `.github` repo

why

• Reduce nested levels of reusable workflows

Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#129)

## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` action

why

• The ReviewDog action will comment with line-level suggestions based on linting failures

Update GitHub workflows @osterman (#128)

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

v0.36.0

What's Changed

• Add GitHub Settings by @osterman in #125
• feat: allow overriding the dynamodb table name by @nitrocode in #126
• Use GitHub Action Workflows from cloudposse/.github Repo by @osterman in #127

New Contributors

• @nitrocode made their first contribution in #126

Full Changelog: 0.35.1...0.36.0

v0.35.1

🚀 Enhancements

feat: adding the option to disable ttl once it was enable before @alfredo-gil (#111)

what

The change aims to be able to disable the TTL once a dynamodb table was enabled before.

why

• With the current dynamic block on the TTL option inside the aws_dynamodb_table resource if you change the var.ttl_enabled = false there are no changes on the infrastructure and the TTL is not disabled:
  No changes. Your infrastructure matches the configuration.
• With this change you can disable the TTL on a dynamodb table that had it enabled before following this process:

• Change the var.ttl_enabled = false Do the plan and apply
• Change later the var.ttl_attribute="" or leave it empty to consolidate the state. If you don't do this second change your plan is going to say something like this and if you try to apply you will have an error...

 ~ resource "aws_dynamodb_table" "default" {
        id                          = "test"
        name                        = "test"
        tags                        = {
            ...
        }
        # (9 unchanged attributes hidden)

      ~ ttl {
          + attribute_name = "ttl"
            # (1 unchanged attribute hidden)
        }

        # (3 unchanged blocks hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Do you want to perform these actions in workspace "test"?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

module.dynamodb["test"].module.dynamodb_table.aws_dynamodb_table.default[0]: Modifying... [id=test]
╷
│ Error: updating Amazon DynamoDB Table (test): updating Time To Live: ValidationException: TimeToLive is already disabled
│ 	status code: 400, request id: XXXXXXXXXXXXXXXXXXXXXX
│
│   with module.dynamodb["test"].module.dynamodb_table.aws_dynamodb_table.default[0],
│   on .terraform/modules/dynamodb.dynamodb_table/main.tf line 46, in resource "aws_dynamodb_table" "default":
│   46: resource "aws_dynamodb_table" "default" {
│

references

• This is the origin of the issue hashicorp/terraform-provider-aws#10304

🤖 Automatic Updates

Update Scaffolding @osterman (#123)

what

• Reran make readme to rebuild README.md from README.yaml
• Migrate to square badges
• Add scaffolding for repo settings and Mergify

why

• Upstream template changed in the .github repo
• Work better with repository rulesets
• Modernize look & feel

v0.35.0

Add support for the import_table block @johncblandii (#120)

what

• Added support for the import_table block

why

• This adds support for using S3 data to import into a new table

references

v0.34.0

Issue 110: Add enable deletion protection @ignacioSuay (#112)

what

Add deletion_protection_enabled to the module. This feature is already available in terraform resource.

why

Terraform dynamodb_table resource has the optional parameter:
deletion_protection_enabled - (Optional) Enables deletion protection for table. Defaults to false.

We would like to be able to use the flag to avoid accidentally deleting DynamoDB tables. Therefore, we would like to add an extra variable to the module to enable/disable deletion protection.

references

This PR is related to the issue raise by the community:
#110

Sync github @max-lobur (#113)

Rebuild github dir from the template

🤖 Automatic Updates

Update README.md and docs @cloudpossebot (#117)

what

This is an auto-generated PR that updates the README.md and docs

why

To have most recent changes of README.md and doc from origin templates

v0.33.0

• No changes

v0.32.0

fix: required aws provider version update @ivanmartos (#108)

what

Update required aws provider version

why

Changes introduced in #107 require aws provider functionality added in https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#4220-july--8-2022

This is current terraform plan output with old aws provider

Error: Unsupported argument

  on .terraform/modules/example.foo_table/main.tf line 112, in resource "aws_dynamodb_table" "default":
 112:       propagate_tags         = false

An argument named "propagate_tags" is not expected here.

Error: Unsupported argument

  on .terraform/modules/example.foo_table/main.tf line 113, in resource "aws_dynamodb_table" "default":
 113:       point_in_time_recovery = false

An argument named "point_in_time_recovery" is not expected here.

references

Release notes for aws provider https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md#4220-july--8-2022

v0.31.0

Fix Perma-Drift with Replicas @milldr (#107)

what

• Explicitly set replica attributes as the default values

why

• If using replicas, we always see drift for plans if those values are not set

references

• closes #104

v0.30.0

Chore: add table_class option @QuentinBtd (#106)

what

Adding table_class option

why

This option can be usefull for tables with infrequent access. It can reduce costs by up to 60%.

references

https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/dynamodb_table#table_class
https://aws.amazon.com/fr/dynamodb/standard-ia/

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

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

🚀 Enhancements

Don't set read/write capacity in PAY_PER_REQUEST billing mode @alexjurkiewicz (#101)

This causes errors at plan-time now:

Error: 2 errors occurred:
	* read_capacity can not be set when billing_mode is "PAY_PER_REQUEST"
	* write_capacity can not be set when billing_mode is "PAY_PER_REQUEST"

  with module.dynamodb_table.aws_dynamodb_table.default[0],
  on .terraform/modules/dynamodb_table/main.tf line 46, in resource "aws_dynamodb_table" "default":
  46: resource "aws_dynamodb_table" "default" {