v0.11.3

Update README.yaml @garym-krrv (#48)

ram_principal is deprecated as per source code.
We should now be using ram_principals variable in the module

what

why

references

🤖 Automatic Updates

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

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 (#46)

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 (#45)

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 (#44)

what

• Update workflows (.github/workflows/settings.yaml)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#43)

what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Add GitHub Settings @osterman (#42)

what

• Install a repository config (.github/settings.yaml)

why

• Programmatically manage GitHub repo settings

v0.11.2

Configurable timeoutes @hans-d (#40)

what

• Replace hardcoded (but default) timeout for aws_route with configurable one

why

• more flexibilty needed re tiemouts

🤖 Automatic Updates

Update Scaffolding @osterman (#39)

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

🚀 Enhancements

Updating default value description to match actual default value @joshuabalduff (#26)

what

default_route_table_association and default_route_table_propagation are set to disable so the description should reflect default values that to avoid possible confusion.

why

So it matches :) unless the default value really should be enable

references

🤖 Automatic Updates

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

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

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

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 (#33)

Rebuild github dir from the template

v0.10.0

• No changes

v0.9.1

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

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

🚀 Enhancements

Bump aws provider to v4.4.0 @nitrocode (#23)

what

• Bump aws provider to v4.4.0

why

• Prevent people from using an older provider version which would cause issues

references

• https://github.com/hashicorp/terraform-provider-aws/releases/tag/v4.4.0
• Previous PR #20
• Closes #24

v0.9.0

Support multiple RAM principals @alexjurkiewicz (#19)

Introduce new variable var.ram_principals, and deprecate
var.ram_principal. Deprecating rather than removing the old variable is
a lot more complex, code-wise, but the complexity is contained and
should ease the upgrade path for existing customers.

Fixes #14

v0.8.0

Allow manually specifying Transit Gateway description @alexjurkiewicz (#18)

v0.7.0

Add var.transit_gateway_cidr_blocks @alexjurkiewicz (#20)

v0.6.1

🚀 Enhancements

Output `ram_resource_share_id` @nitrocode (#17)

what

• Output ram_resource_share_id

why

• In case additional principals need to be associated to the ram resource share
• At the moment, if var.ram_principal is passed in, the org data source is replaced, and there is no way to pass in multiple ram principals
• Easiest solution is to export the ram resource share id and associate from outside the module

references

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ram_principal_association