v1.0.2

Support for additional policy for creating reserial copies of S3 buckets @obervinov (#89)

## what

• Added an additional policy (AWSBackupServiceRolePolicyForS3Backup) to the IAM user being created.
• This allows the module to be used for creating backups of S3 buckets.

why

• Backing up S3 buckets was a missing feature necessary to fully cover the backup process through AWS Backup using this module.
• The IAM user created by this module lacked the additional AWSBackupServiceRolePolicyForS3Backup policy needed for S3 bucket backups.

references

• #88

🤖 Automatic Updates

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

## 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 .github/settings.yml @osterman (#90)

## 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

v1.0.1

fix: null value reference when copy_action is specified without lifecycle options @carlosaml (#86)

what

Attempt to get attribute from null value error when a copy_action is specified in a backup rule without any lifecycle options

steps to reproduce

Based on the complete example:

module "backup" {
  source = "../.."

  backup_resources = [module.efs.arn]
  not_resources    = var.not_resources

  rules = [
    {
      name              = "${module.this.name}-daily"
      schedule          = var.schedule
      start_window      = var.start_window
      completion_window = var.completion_window
      lifecycle = {
        cold_storage_after = var.cold_storage_after
        delete_after       = var.delete_after
      }
      copy_action = {
        destination_vault_arn = "arn:aws:backup:us-east-2:123456789000:backup-vault:my-vault"
      }
    }
  ]

  backup_vault_lock_configuration = {
    max_retention_days = 365
    min_retention_days = 30
  }

  context = module.this.context
}

why

The following error should not happen:

╷
│ Error: Attempt to get attribute from null value
│
│   on ../../main.tf line 79, in resource "aws_backup_plan" "default":
│   79:               cold_storage_after = rule.value.copy_action.lifecycle.cold_storage_after
│     ├────────────────
│     │ rule.value.copy_action.lifecycle is null
│
│ This value is null, so it does not have any attributes.
╵
╷
│ Error: Attempt to get attribute from null value
│
│   on ../../main.tf line 80, in resource "aws_backup_plan" "default":
│   80:               delete_after       = rule.value.copy_action.lifecycle.delete_after
│     ├────────────────
│     │ rule.value.copy_action.lifecycle is null
│
│ This value is null, so it does not have any attributes.
╵

🚀 Enhancements

chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @renovate (#70)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/dynamic-subnets/aws (source)	module	patch	2.4.1 -> 2.4.2

---

Release Notes

cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)

v2.4.2

Compare Source

🚀 Enhancements

chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	minor	1.3.0 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;jasonmk (#&#​8203;31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​&#​8203;max-lobur (#&#​8203;27)

Rebuild github dir from the template

---

🤖 Automatic Updates

chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	minor	1.3.0 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;jasonmk (#&#​8203;31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​&#​8203;max-lobur (#&#​8203;27)

Rebuild github dir from the template

---

Update README.md and docs @​cloudpossebot (#​189)

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

---

🤖 Automatic Updates

chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @renovate (#70)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/dynamic-subnets/aws (source)	module	patch	2.4.1 -> 2.4.2

---

Release Notes

cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)

v2.4.2

Compare Source

🚀 Enhancements

chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	minor	1.3.0 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;jasonmk (#&#​8203;31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​&#​8203;max-lobur (#&#​8203;27)

Rebuild github dir from the template

---

🤖 Automatic Updates

chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/utils/aws (source)	module	minor	1.3.0 -> 1.4.0

---

Release Notes

cloudposse/terraform-aws-utils (cloudposse/utils/aws)

v1.4.0

Compare Source

Add il-central-1 region @​&#​8203;jasonmk (#&#​8203;31)

what

Add new Tel Aviv (il-central-1) region

why

Provide full coverage

references

Sync github @​&#​8203;max-lobur (#&#​8203;27)

Rebuild github dir from the template

---

Update README.md and docs @​cloudpossebot (#​189)

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

---

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

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

chore(deps): update terraform cloudposse/efs/aws to v1 @renovate (#68)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/efs/aws (source)	module	major	0.36.0 -> 1.1.0 ...

1.0.0

What's Changed

• Sync github by @max-lobur in #51
• add aws_backup_vault_lock_configuration by @Benbentwo in #61
• major update: remove deprecated, singular rule type by @Benbentwo in #63

Full Changelog: 0.14.1...1.0.0

v0.14.1

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

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

Seems like we're still experiencing some issues with this release.

What's Changed

• Support multiple schedules per plan by @nightspotlight in #39
• Hotfix Issue with 0.14.0 datastructure by @Benbentwo in #42
• Multiple rules by @nitrocode in #43

New Contributors

• @nightspotlight made their first contribution in #39

Full Changelog: 0.13.1...0.14.0

v0.13.1

🚀 Enhancements

Add role outputs @nitrocode (#40)

what

• Add role outputs
• Remove unused providers

why

• Allow adding additional policies to role from outside of the module

references

• Related to #37

v0.13.0

Add support for permissionsboundary on IAM Role @dennisbrouwer91 (#36)

what

• This PR adds support for PermissionBoundaries in AWS on IAM Role creation

why

• We use AWS accounts with a PermissionsBoundary (which is enforced), without this change we can't use the module

references

(https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_boundaries.html)

v0.12.0

Add not_resources @stratusjerry (#34)

what

• Adds the not_resources argument

why

• adds functionality

v0.11.0

Allow override resource names @max-lobur (#32)

what

• Allow override resource names
• This change is fully backwards compatible, it does not break any of the previous use cases.

why

• Helps building multi-policy backup schemas for a single vault

v0.10.5

🤖 Automatic Updates

Update Terraform cloudposse/label/null to v0.25.0 @renovate (#28)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/label/null (source)	module	minor	0.24.1 -> 0.25.0

---

Release Notes

cloudposse/terraform-null-label

v0.25.0

Compare Source

Add "tenant", "labels_as_tags", and "descriptors" @​Nuru (#​132)

#### what - Add additional label and `id` component: `tenant` - New input `labels_as_tags` controls which labels are exported as tags - New input `descriptor_formats` generates new output `descriptors` - Update README, remove link to obsolete `terraform-terraform-label` #### why - Support users that host resources on behalf of and/or dedicated to single customers - Supersedes and closes #​131, giving people control over which tags the module generates - Simple mechanism for creating multiple identifiers from the same inputs, reducing the need to create multiple instances of `null-label` - Document `tenant`, `labels_as_tags`, `descriptor_formats`, add additional clarification, stop promoting obsolete module

Fix: Update README Snippets @​korenyoni (#​130)

#### what * Update README snippets to reflect use of Terraform Registry. #### why * Including snippets that reflect use of the Terraform Registry make it easier for users to quickly instantiate a null_label module. * README is out of date and does not include snippets that reflect use of the Terraform Registry. #### references * N/A

Bridgecrew compliance @​Nuru (#​125)

#### what - Resolve Bridgecrew compliance complaint about example Autoscaling Group (BC_AWS_GENERAL_31) - Fix typo in README - Include Terraform lock file in `.gitignore` #### why - Get clean Bridgecrew badge - Correct confusing error - Ensure lock files are not checked into GitHub #### note The PR can and should be merged into `master` to update README and Bridgecrew without triggering a new release/version. These changes have no effect on the actual module in use and a release will create unnecessary ripple effects. However, merging to `master` will update the README and badges, so is worthwhile, and the changes will move forward into the next release.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.