Skip to content

Releases: cloudposse/test-helpers

v0.5.0

15 Apr 19:38
5557c58
Compare
Choose a tag to compare
Update module github.com/rebuy-de/aws-nuke/v2 to v2.25.0 @renovate (#13)

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/rebuy-de/aws-nuke/v2 v2.20.0 -> v2.25.0 age adoption passing confidence

Release Notes

rebuy-de/aws-nuke (github.com/rebuy-de/aws-nuke/v2)

v2.25.0

Compare Source

What's Changed

Chores

New Contributors

Full Changelog: rebuy-de/aws-nuke@v2.24.2...v2.25.0

v2.24.2

Compare Source

What's Changed

Chores

Full Changelog: rebuy-de/aws-nuke@v2.24.1...v2.24.2

v2.24.1

Compare Source

What's Changed

Chores

Full Changelog: rebuy-de/aws-nuke@v2.24.0...v2.24.1

v2.24.0

Compare Source

What's Changed

Read more

v0.4.0

15 Apr 16:40
dce7021
Compare
Choose a tag to compare
Configure Renovate @renovate (#2)

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.


Detected Package Files

  • .github/workflows/auto-release.yml (github-actions)
  • .github/workflows/test.yml (github-actions)
  • .github/workflows/validate-codeowners.yml (github-actions)
  • go.mod (gomod)

Configuration Summary

Based on the default config's presets, Renovate will:

  • Start dependency updates only once this onboarding PR is merged
  • Show all Merge Confidence badges for pull requests.
  • Enable Renovate Dependency Dashboard creation.
  • Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
  • Ignore node_modules, bower_components, vendor and various test/tests directories.
  • Group known monorepo packages together.
  • Use curated list of recommended non-monorepo package groupings.
  • Apply crowd-sourced package replacement rules.
  • Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.


What to Expect

With your current configuration, Renovate will create 10 Pull Requests:

Update module github.com/gruntwork-io/terratest to v0.46.13
Update mszostok/codeowners-validator action to v0.7.4
  • Schedule: ["at any time"]
  • Branch name: renovate/mszostok-codeowners-validator-0.x
  • Merge into: main
  • Upgrade mszostok/codeowners-validator to v0.7.4
Update module github.com/aws/aws-sdk-go to v1.51.21
  • Schedule: ["at any time"]
  • Branch name: renovate/aws-sdk-go-monorepo
  • Merge into: main
  • Upgrade github.com/aws/aws-sdk-go to v1.51.21
Update module github.com/hashicorp/terraform-json to v0.21.0
Update module github.com/jinzhu/copier to v0.4.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-jinzhu-copier-0.x
  • Merge into: main
  • Upgrade github.com/jinzhu/copier to v0.4.0
Update module github.com/rebuy-de/aws-nuke/v2 to v2.25.0
Update module github.com/stretchr/testify to v1.9.0
  • Schedule: ["at any time"]
  • Branch name: renovate/github.com-stretchr-testify-1.x
  • Merge into: main
  • Upgrade github.com/stretchr/testify to v1.9.0
Update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to v4
Update actions/setup-go action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-setup-go-5.x
  • Merge into: main
  • Upgrade actions/setup-go to v5
Update aws-actions/configure-aws-credentials action to v4

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.


❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.


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

v0.3.0

15 Apr 16:38
fcfc4a4
Compare
Choose a tag to compare
add atmos support @mcalhoun (#4)

what

  • Add support to the helpers library to allow running atmos tests

why

  • This gives us the ability to model different functionality of a component as atmos stacks, or different variables of a single atmos stack and run tests against them. This will allow us to get better test coverage for out reference architecture components.

Summary by CodeRabbit

  • New Features

    • Introduced new functionalities for running commands, applying configurations, and handling Terraform operations using the Atmos tool.
    • Added enhanced documentation in README.md, including updated installation instructions and examples.
    • New basic and complex Terraform configurations for testing various scenarios.
  • Documentation

    • Significantly updated the README.md file to improve structure, clarity, and content completeness.
  • Tests

    • Added comprehensive tests for new functionalities in the Atmos package, covering scenarios like idempotency and error handling.
    • Introduced new test fixtures to support varied Terraform configurations.
  • Chores

    • Updated .gitignore and GitHub Actions workflow to better support development and testing processes.
  • Refactor

    • Replaced testacc target in Makefile with a more comprehensive test target using updated tools and configurations.
Auto release fix @goruha (#5)

What

  • Use auto relesase shared workflow

Why

v0.2.0

31 Jan 17:39
f3f47ba
Compare
Choose a tag to compare
Consolidate auto-release workflow @goruha (#3)

what

  • Use cloudposse/github-action-auto-release in auto-release.yaml workflow

why

  • Solve old nodejs warning
  • Reduce duplication of code

v0.1.0

07 Nov 15:26
0e85103
Compare
Choose a tag to compare
initial implementation @mcalhoun (#1)

what

  • Add helpers to allow aws-nuke to be called from terratest tests

why

  • When developing terraform modules and components for AWS, it is a frequent occurrence that something goes wrong during the process and leaves orphaned resources. Using these helper functions, we can ensure the test AWS account is cleaned up after our tests.