Skip to content

v0.26.0

Compare
Choose a tag to compare
@cloudposse-releaser cloudposse-releaser released this 29 Jun 07:27
· 16 commits to refs/heads/main since this release
test: update test framework to use latest best practices and reduce boilerplate @gmeligio (#100)

what

Update this module's test framework. Reduce boilerplate and make reusable functions.

Changelog:

  1. Upgrade go to 1.21.
  2. Update test/Makefile and test/src/Makefile from https://github.com/cloudposse/terraform-aws-eks-node-group/tree/e9f908c026d8ca5dc30190a050de68a510ff3983/test
  3. Create framework_test.go and default_test.go, following how it's done in https://github.com/cloudposse/terraform-aws-eks-node-group/blob/e9f908c026d8ca5dc30190a050de68a510ff3983/test/src/framework_test.go
  4. Remove enabled=true from fixtures and add new test TestExamplesCompleteDisabled for when enabled=false
  5. Add Test_ExistingDeployment for faster test cycle, and modify Makefile accordingly
  6. Update dependencies
  7. Migrate test DB Engine from 3.6.0 to 5.0.0

why

  • Enable testing with OpenTofu
  • Support automated maintenance

references

[CHORE] Update variable description @RuiSMagalhaes (#99)

what

  • Updates enabled_cloudwatch_logs_exports variable description
  • Updates examples
  • Updates README.md and docs/terraform.md

why

  • Ir order to have the right list of logs available in the variable description

references

🚀 Enhancements

feat(aws_docdb_cluster): add allow_major_version_upgrade argument @gmeligio (#94)

what

This PR adds the argument allow_major_version_upgrade that was released in https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.21.0

It includes with the changes in the test framework from #100 .

why

When upgrading the engine_version to a new major version, allow_major_version_upgrade needs to be enabled for AWS to apply the upgrade.

references

🤖 Automatic Updates

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

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

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

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

what

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

why

  • Support new readme generation workflow.
  • Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#91)

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

what

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

why

  • Programmatically manage GitHub repo settings
Update Scaffolding @osterman (#87)

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
Update README.md and docs @cloudpossebot (#83)

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