v0.48.1

🤖 Automatic Updates

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

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

Terraform 0.14 upgrade @maximmi (#112)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.47.0

chore(deps): update mszostok/codeowners-validator action to v0.6.0 @renovate (#115)

This PR contains the following updates:

Package	Type	Update	Change
mszostok/codeowners-validator	action	minor	v0.5.0 -> v0.6.0

---

Release Notes

mszostok/codeowners-validator

v0.6.0

Compare Source

🚨GitHub Codeowners Validator 0.6.0 is now available!

Highlights

• ✨ Add validation for checking if team has a proper permission
  Due to the new permission validation step in Owners Checker, this check takes a little more time.

• 🐛 Fix bug in Owners Checker. Now Owners Checker supports child teams with inherited repo perms.

• ⚠️ Error message was changed in Owners Checker.
  From
  [err] line 15: Team "avengers" does not have permissions associated with the repository "codeowners-samples".
  To
  [err] line 15: Team "avengers" does not exist in organization "gh-codeowners" or has no permissions associated with the repository.

Installation

To install the codeowners-validator, run:

Install codeowners-validator in /usr/local/bin in version 0.6.0

curl -sfL https://raw.githubusercontent.com/mszostok/codeowners-validator/master/install.sh| sh -s -- -b /usr/local/bin v0.6.0

See the Installation section for more installation options.

Docker images

• docker pull mszostok/codeowners-validator:latest
• docker pull mszostok/codeowners-validator:v0.6.0
• docker pull mszostok/codeowners-validator:v0.6

Changelog 🚀

8fafb0b Adjust docs and GitHub action for v0.6.0 release
2f6e3bb Fix badly worded error (#​64)
5ed7b98 Adjust integration test after changing error message
204640e address comments from PR #​62
9224144 Add permissions check to valid_owner
cde24ed Add a twitter badge
e5e11b0 rename test to comply with golang.org/x/mod/module.CheckFilePath (#​60)

Contributors

Thanks again to everyone who contributed to this release! ✨

Users whose commits are in this release:

• @​mszostok
• @​jspiro
• @​highb
• @​sgmitchell

v0.5.1

Compare Source

Changelog

d6bdfac Add CONTRIBUTING.md and development.md (#​56)
4f46df1 Add configurability for the list of ignored owners (#​55)
085f270 Adjust docs and GitHub action for v0.5.1 release
97fb795 Ignore ghost user (#​53)
0b6c2ef Update info about new checker (#​51)

Docker images

• docker pull mszostok/codeowners-validator:latest
• docker pull mszostok/codeowners-validator:v0.5.1
• docker pull mszostok/codeowners-validator:v0.5

---

Renovate configuration

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

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

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

v0.46.2

🤖 Automatic Updates

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

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

🚀 Enhancements

Terraform 0.14 upgrade @maximmi (#110)

what

• Upgrade to support Terraform 0.14 and bring up to current Cloud Posse standard

why

• Support Terraform 0.14

v0.46.0

Add resourceRequirements key @karvounis (#107)

what

• The key resourceRequirements is added based on https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html
• Very simple addition of one variable that is a list of ResourceRequirement objects https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ResourceRequirement.html

why

• The key resourceRequirements was missing and I was not able to add a GPU requirement to the container definition

references

• https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ContainerDefinition.html
• https://docs.aws.amazon.com/AmazonECS/latest/APIReference/API_ResourceRequirement.html
• #105
• closes #105

v0.45.2

chore(deps): update cloudposse/actions action to v0.21.0 @renovate (#103)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/actions	action	minor	0.16.0 -> 0.21.0

---

Release Notes

cloudposse/actions

v0.21.0

Compare Source

Update GitHub actions to replace deprecated set-env (#​58)

notes

• Actions calling any of the following affected commands need to be updated:
  • test-command
  • repository-dispatch
  • slash-command-dispatch
  • create-or-update-comment
• New version of create-or-update-comment deprecates reaction-type in favor of comma-separated list of reactions. Actions calling create-or-update-comment should switch to reactions.
• auto-approve-action and auto-assign-action not updated because the sources have not yet been updated to replace set-env

v0.20.0

Compare Source

v0.19.0

Compare Source

what

• Add GitHub Actions job to test on AWS & Datadog

why

• We have repos that require provisioning Datadog resources that need DD credentials
• In the new job, we use ENV variables DD_API_KEY and DD_APP_KEY to specify api_key and app_key to the Datadog terraform provider

v0.18.0

Compare Source

what

• update version for auto-merge
• update version for auto-approve

v0.17.0

Compare Source

---

Renovate configuration

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

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

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

v0.45.1

Configure Renovate @renovate (#98)

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/chatops.yml (github-actions)
• versions.tf (terraform)

Configuration Summary

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

• Start dependency updates only once this onboarding PR is merged
• Separate major versions of dependencies into individual branches/PRs
• Do not separate patch and minor upgrades into separate PRs for the same dependency
• Upgrade to unstable versions only if the existing version is unstable
• Raise PRs immediately (after branch is created)
• If semantic commits detected, use semantic commit type fix for dependencies and chore for all others
• Keep existing branches updated even when not scheduled
• Disable automerging feature - wait for humans to merge all PRs
• Ignore node_modules, bower_components, vendor and various test/tests directories
• Autodetect whether to pin dependencies or maintain ranges
• Rate limit PR creation to a maximum of two per hour
• Limit to maximum 20 open PRs at any time
• Group known monorepo packages together
• Use curated list of recommended non-monorepo package groupings
• Ignore wrongly tagged actions/setup-node v2 releases

🔡 Would you like to change the way Renovate is upgrading your dependencies? Simply edit the renovate.json in this branch with your custom config and the list of Pull Requests in the "What to Expect" section below will be updated the next time Renovate runs.

---

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

Update cloudposse/actions action to v0.21.0

• Schedule: ["at any time"]
• Branch name: renovate/cloudposse-actions-0.x
• Merge into: master
• Upgrade cloudposse/actions to 0.21.0

---

❓ 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 WhiteSource Renovate. View repository job log here.

v0.45.0

Module modernisation @joe-niland (#102)

what

• relax provider pinning
• add chatops
• add autorelease
• use new terratest structure

why

• Allow this module to be consumed by modules using later version of providers
• Add gitops automation

references

• closes #101

0.44.0: Force user to "0" when firelens is set (#97)

* Force user to "0" when firelens is set

Recently I started experiencing apply churn in my runs. I eventually traced it down to a behavior with Firelens enabled task.

If one submits a firelens-enabled task definition with `user=null`, AWS helpful replaces the value with `"0"`. This causes Terraform to repeatedly try to fix the discrepancy. This change aims to address this edge-case behavior which I found to be unintuitive.

                  ~ user                   = "0" -> null

Additionally, attempting to set the `user` to any value _other_ than `"0"` (or null) is an error:

                  ~ user                   = "0" -> "root"
    ...
    Error: ClientException: If 'user' field is specified on firelens container, then 'UID' has to be '0'.

Which simplifies our ternary, so that's nice. It would have preferred to deal with this with a [custom validation rule](https://www.terraform.io/docs/configuration/variables.html#custom-validation-rules), unfortunately that doesn't support checking multiple inputs so it's not viable here.

* Executed 'terraform fmt'

* Updated README.md

Co-authored-by: actions-bot <[email protected]>