Releases: cloudposse/terraform-example-module
Releases · cloudposse/terraform-example-module
v3.0.1
Fix readme yaml Igor Rodionov (@goruha) (#75)
## what * Fix readme yamlwhy
- There were empty settings after getting rid of multiple docs in
README.yaml
references
Use new readme action Igor Rodionov (@goruha) (#71)
## what * Use new readme action * Remove the multi-doc YAML hack to `README.yaml` which was added to make it more obvious to developers when they forget to change the boilerplate.why
actions-tools/yaml-outputsdoesn't support multi-doc
🤖 Automatic Updates
Update GitHub Workflows to Fix ReviewDog TFLint Action Erik Osterman (Cloud Posse) (@osterman) (#74)
## what - Update workflows (`.github/workflows`) to add `issue: write` permission needed by ReviewDog `tflint` actionwhy
- The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows Erik Osterman (Cloud Posse) (@osterman) (#73)
## what - Update workflows (`.github/workflows/settings.yaml`)why
- Support new readme generation workflow.
- Generate banners
v3.0.0
acceptance-test Igor Rodionov (@goruha) (#69)
## what- Acceptance test release workflow
🤖 Automatic Updates
Use GitHub Action Workflows from `cloudposse/.github` Repo Erik Osterman (Cloud Posse) (@osterman) (#68)
## what- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.githubrepository - Simplify management of workflows from centralized hub of configuration
v2.0.0
Test release workflow Igor Rodionov (@goruha) (#67)
## what * Test release workflowUpdate settings.yml Igor Rodionov (@goruha) (#66)
## what- Update settings.yml
test-relese2-env Igor Rodionov (@goruha) (#64)
## what- test-relese2-env
Test different environment Igor Rodionov (@goruha) (#63)
## what- Test different environment
test-custom-branches-settings Igor Rodionov (@goruha) (#62)
## what- test-custom-branches-settings
Update settings.yml Igor Rodionov (@goruha) (#61)
## what- Test custom tags settings
v1.1.0
test-release-workflow Igor Rodionov (@goruha) (#60)
## what- test-release-workflow
Release published fix Igor Rodionov (@goruha) (#59)
## what- Release published workflow fix
v1.0.1
Fix feature branch workflow Igor Rodionov (@goruha) (#58)
## what- Do not trigger feature branch workflow on
labelunlabel
why
- There is no operation that we need to perform on labels
New release workflows Igor Rodionov (@goruha) (#57)
## what- New release workflows
Sync github Max Lobur (@max-lobur) (#45)
Rebuild github dir from the templateRemove stale workflow Max Lobur (@max-lobur) (#43)
## what * Remove stale chatops workflowwhy
- Cleanup
Add ChatOps workflow Max Lobur (@max-lobur) (#42)
## what * Adds ChatOps workflowwhy
- Migrating onto new shared workflows
Add scheduled workflows Max Lobur (@max-lobur) (#41)
## what * Add scheduled workflowwhy
- Implement cloudposse/github-actions-workflows-terraform-module#6 in module template repo
Unify workflow naming Max Lobur (@max-lobur) (#40)
## what * Unify workflow namingwhy
- Unifying across all workflows
Shared workflows Max Lobur (@max-lobur) (#38)
## what * Use the new shared workflows for terraformwhy
- Reduce boilerplate
links
Testing in https://github.com/cloudposse/terraform-module-test
Update test dependencies for go 1.19 Nuru (@Nuru) (#29)
## what - Update test dependencies for go 1.19why
- Stay current with security patches
notes
- Supersedes and closes #28
🤖 Automatic Updates
Add GitHub Settings Erik Osterman (Cloud Posse) (@osterman) (#51)
## what - Install a repository config (`.github/settings.yaml`)why
- Programmatically manage GitHub repo settings
Update Scaffolding Erik Osterman (Cloud Posse) (@osterman) (#49)
## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for repo settings and Mergifywhy
- Upstream template changed in the
.githubrepo - Work better with repository rulesets
- Modernize look & feel
Update Scaffolding Erik Osterman (Cloud Posse) (@osterman) (#47)
## what - Reran `make readme` to rebuild `README.md` from `README.yaml` - Migrate to square badges - Add scaffolding for repo settings and Mergifywhy
- Upstream template changed in the
.githubrepo - Work better with repository rulesets
- Modernize look & feel
Update README.md and docs Cloud Posse Bot (CI/CD) (@cloudpossebot) (#46)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
Update README.md and docs Cloud Posse Bot (CI/CD) (@cloudpossebot) (#33)
## what This is an auto-generated PR that updates the README.md and docswhy
To have most recent changes of README.md and doc from origin templates
v1.0.0 Initial release with production Semantic Versioning
Initial release with production Semantic Versioning, part of Cloud Posse's general policy to convert to production versioning as we make updates to relatively mature modules
🚀 Enhancements
Update test dependencies Nuru (@Nuru) (#27)
what
- Update test-framework to current
why
- Bug fixes, style cleanup
v0.8.1
🚀 Enhancements
Fix Disabled test Nuru (@Nuru) (#24)
what
- Update testing of
enabled = false - Fix Makefile to run all tests
- Update
git.io->cloudposse.tools
why
- Proper test structure
- Was running only a single test even when multiple tests were present
- EOL for
git.io
v0.8.0
Testing with Go 1.17 and Terratest 0.39.0 Nuru (@Nuru) (#22)
what && why
- Update
goversion use in tests from 1.16 to 1.17 for security fixes - Revert
terratestfrom 0.40.0 to 0.39.0 to ensure support for Terraform version < 1.1 - Update boilerplate to stay current
v0.7.1
🚀 Enhancements
fix a few small bugs Matt Calhoun (@mcalhoun) (#20)
what
- Update incorrect provider config
- Remove unused variable
- Add
.terraform.lock.hclto the.gitignore
why
- The main driver for this PR was that we previously had:
required_providers {
local = {
source = "hashicorp/aws"
version = ">= 3.0"
}
}
}This lead to a misconfiguration which caused the AWS provider not to function properly and lead to several hours of debugging.
v0.7.0
Update testing framework, other maintenance Nuru (@Nuru) (#18)
what
- Update testing framework to current standards
- Update module framework files to current
- Make README for this repo a bit more relevant while making README template better for new repos
why
- Projects using this as a template were failing testing due to problems in this repo
