Skip to content

Releases: cloudposse-archives/turf

v0.20.0

01 May 17:26
a4d6a82
Compare
Choose a tag to compare
  • No changes

v0.19.0

01 May 17:25
a4d6a82
Compare
Choose a tag to compare
Update github output syntax @max-lobur (#56) ## what Update github output syntax

why

Following github docs

references

https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

v0.18.0

01 Jul 20:25
920d144
Compare
Choose a tag to compare
git.io->cloudposse.tools update @dylanbannon (#50) ## 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

v0.17.0

12 May 16:46
102ddf9
Compare
Choose a tag to compare
add missing control @mcalhoun (#43) ## what
  • Add a missing control to disable in non-Cloudtrail accounts

why

  • The Avoid the use of the "root" account log metric filter should only be enabled in the global collection region of the CloudTrail account.

v0.16.0

19 Apr 14:55
950c68c
Compare
Choose a tag to compare
updates to support priv sessions @mcalhoun (#41) ## what
  • Update to support privileged session for the security hub disable-global-control command
  • Add retry logic to UpdateStandardsControl

why

  • When using AWS SSO and a profile, it is not necessary to assume a separate role
  • When disabling a large number of controls, we often got 429 rate limit exceeded messages, so the retry logic deals with that

v0.15.0

15 Apr 15:43
048fecd
Compare
Choose a tag to compare
  • No changes

v0.14.0

15 Apr 15:43
048fecd
Compare
Choose a tag to compare
allow security hub disable controls to run without role @mcalhoun (#39) ## what

Allow use of the current session in the aws disable-global-controls command via the --privileged flag rather than specifying a role ARN

why

When using an IAM user or AWS SSO, the user can run with the currently exported credentials (or specify a profile) rather than a role ARN. In the following example, the user would be deleting all the Security Hub Global Controls in the security account:

$ AWS_PROFILE=acme-gbl-security-admin turf aws disable-global-controls --global-collector-region us-east-1 --privileged
revert change excluding ap-northeast-3 @mcalhoun (#40) # what
  • Revert change excluding ap-northeast-3 region from the enabled regions API call

why

  • The AWS SDK for Go now generates endpoints for the ap-northeast-3 region and an issue has been closed.

v0.13.0

24 Mar 13:41
97fd006
Compare
Choose a tag to compare
allow use of privileged session @mcalhoun (#36) ## what

Allow use of the current session in the aws delete-default-vpcs command via the --privileged flag rather than specifying a role ARN

why

When using an IAM user or AWS SSO, the user can run with the currently exported credentials (or specify a profile) rather than a role ARN. In the following example, the user would be deleting all the VPCs in the security account:

$ AWS_PROFILE=acme-gbl-security-admin turf aws delete-default-vpcs --privileged --delete

v0.12.0

04 Mar 17:12
f32541c
Compare
Choose a tag to compare
filter out ap-northeast-3 region @mcalhoun (#33) # what
  • Exclude ap-northeast-3 region from the enabled regions API call
  • Remove some redundant type specifications
  • Update the docs to be more clear on what is deleted when VPCs are deleted

why

  • The AWS SDK for Go currently doesn't generate endpoints for the ap-northeast-3 region and an issue has been opened to track this.

v0.11.0

03 Feb 01:13
43f9ee6
Compare
Choose a tag to compare
fix broken badges @mcalhoun (#24) ## what

Update the status badges for CI Builds

why

They were broken previously