v0.9.0

Adding the ability to change the instance reuse policy in an autoscale group @ekawas-vrify (#46)

## what

Adding the ability to set the instance_reuse_policy so that warm pools can reuse instances on scale in if wanted.

why

I needed to be able to reuse my instances in a warm pool because the base images are quite large. The terraform-aws-ec2-autoscale-group module already supports it and this change exposes it.

references

v0.8.0

Added custom name to capacity provider @carlolucadei (#51)

## what

We added the way to customize the capacity provider name

why

With the current change the default behaviour is preserved.
We applied this in order to avoid issues while creating a new capacity provider for another environment since for AWS it already exists due to a previous deploy ie in test env.

v0.7.0

feat: add throughput option to block_device_mappings @Moncky (#53)

## what

This change adds the through put option to the ebs block_device_mappints object in the capacity_providers_fargate_ec2 variable

why

Support to tune the throughput of the ebs volumes was added to the autoscaling group module in version 0.37.1. As it is not defined in the option block here its not passed through during an execution.

references

Release notes for 0.37.1 of cloudposse/terraform-aws-ec2-autoscale-group

Closes #52

🤖 Automatic Updates

Migrate new test account @osterman (#54)

## what - Update `.github/settings.yml` - Update `.github/chatops.yml` files

why

• Re-apply .github/settings.yml from org level to get terratest environment
• Migrate to new test account

References

• DEV-388 Automate clean up of test account in new organization
• DEV-387 Update terratest to work on a shared workflow instead of a dispatch action
• DEV-386 Update terratest to use new testing account with GitHub OIDC

Update .github/settings.yml @osterman (#50)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

Update .github/settings.yml @osterman (#48)

## what - Update `.github/settings.yml` - Drop `.github/auto-release.yml` files

why

• Re-apply .github/settings.yml from org level
• Use organization level auto-release settings

references

• DEV-1242 Add protected tags with Repository Rulesets on GitHub

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

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

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

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

## what - Update workflows (`.github/workflows/settings.yaml`)

why

• Support new readme generation workflow.
• Generate banners

Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#38)

## what

• Install latest GitHub Action Workflows

why

• Use shared workflows from cldouposse/.github repository
• Simplify management of workflows from centralized hub of configuration

Bump google.golang.org/grpc from 1.49.0 to 1.56.3 in /test/src @dependabot (#36)

Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.49.0 to 1.56.3.

Release notes

Sourced from google.golang.org/grpc's releases.

Release 1.56.3

Security

• server: prohibit more than MaxConcurrentStreams handlers from running at once (CVE-2023-44487)

  In addition to this change, applications should ensure they do not leave running tasks behind related to the RPC before returning from method handlers, or should enforce appropriate limits on any such work.

Release 1.56.2

• status: To fix a panic, status.FromError now returns an error with codes.Unknown when the error implements the GRPCStatus() method, and calling GRPCStatus() returns nil. (#6374)

Release 1.56.1

• client: handle empty address lists correctly in addrConn.updateAddrs

Release 1.56.0

New Features

• client: support channel idleness using WithIdleTimeout dial option (#6263)
  • This feature is currently disabled by default, but will be enabled with a 30 minute default in the future.
• client: when using pickfirst, keep channel state in TRANSIENT_FAILURE until it becomes READY (gRFC A62) (#6306)
• xds: Add support for Custom LB Policies (gRFC A52) (#6224)
• xds: support pick_first Custom LB policy (gRFC A62) (#6314) (#6317)
• client: add support for pickfirst address shuffling (gRFC A62) (#6311)
• xds: Add support for String Matcher Header Matcher in RDS (#6313)
• xds/outlierdetection: Add Channelz Logger to Outlier Detection LB (#6145)
  • Special Thanks: @​s-matyukevich
• xds: enable RLS in xDS by default (#6343)
• orca: add support for application_utilization field and missing range checks on several metrics setters
• balancer/weightedroundrobin: add new LB policy for balancing between backends based on their load reports (gRFC A58) (#6241)
• authz: add conversion of json to RBAC Audit Logging config (#6192)
• authz: add support for stdout logger (#6230 and #6298)
• authz: support customizable audit functionality for authorization policy (#6192 #6230 #6298 #6158 #6304 and #6225)

Bug Fixes

• orca: fix a race at startup of out-of-band metric subscriptions that would cause the report interval to request 0 (#6245)
• xds/xdsresource: Fix Outlier Detection Config Handling and correctly set xDS Defaults (#6361)
• xds/outlierdetection: Fix Outlier Detection Config Handling by setting defaults in ParseConfig() (#6361)

API Changes

• orca: allow a ServerMetricsProvider to be passed to the ORCA service and ServerOption (#6223)

Release 1.55.1

• status: To fix a panic, status.FromError now returns an error with codes.Unknown when the error implements the GRPCStatus() method, and calling GRPCStatus() returns nil. (#6374)

Release 1.55.0

Behavior Changes

• xds: enable federation support by default (#6151)
• status: status.Code and status.FromError handle wrapped errors (#6031 and #6150)

... (truncated)

Commits

• 1055b48 Update version.go to 1.56.3 (#6713)
• 5efd7bd server: prohibit more than MaxConcurrentStreams handlers from running at once...
• bd1f038 Upgrade version.go to 1.5...

v0.6.1

ECS Cluster default Service Discovery Namespace support @Benbentwo (#29)

what

• add support for default service discovery namespace

why

• service discovery acts as a local DNS for all your ECS Services, it is often useful to have an entire cluster of services capable of speaking with one another.

references:

• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecs_cluster#service_connect_defaults

🤖 Automatic Updates

Update Scaffolding @osterman (#28)

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

v0.6.0

Remove default empty value @pagmerek (#25)

what

• Remove default null field in mixed instances policy

why

According to terraform docs:

An optional attribute with a non-null default value is guaranteed to never have the value null within the receiving module. 
Terraform will substitute the default value both when a caller omits the attribute altogether and when a caller explicitly
sets it to null, thereby avoiding the need for additional checks to handle a possible null value. 

In ASG Cloudposse component here you can see that on any value that is not null it will create mixed_instances_policy

references

• related PR in ASG component: cloudposse/terraform-aws-ec2-autoscale-group#126

v0.5.0

Add default null value for mixed_instances_policy @pagmerek (#23)

what

If no mixed_instances_policy is given for ECS cluster alb then we shouldn't set it to the { override = null } value. This causes AWS to see the ALB as one with mixed_instances_policy which disables options like Spot Instances or Warm Pools

why

Without that it is impossible to use Spot Instances / Warm Pools on EC2 capacity providers within this module

v0.4.1

🚀 Enhancements

chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.35.0 (main) @renovate (#21)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ec2-autoscale-group/aws (source)	module	minor	0.34.2 -> 0.35.0

---

Release Notes

cloudposse/terraform-aws-ec2-autoscale-group (cloudposse/ec2-autoscale-group/aws)

v0.35.0

Compare Source

Made spot_options in instance_market_options optional @​skjensen (#​117)

what

Made spot_options in instance_market_options optional.

why

On the AWS Web console there is an option to tick a box that provides guidance on how to create a Launch Template, there works with an EC2 Auto scaling group.

Expanding the "Advanced details" ticking "Request spot instance" you will see most of the options are marked as "Don't include in launch template (recommended)"

Expiry date and Interruption behaviour are not applicable. Having all spot_options as required in this template makes it impossible to enable spot instances in an EC2 Auto Scaling group.

On a related note, but not requiring any change to the module.
The variable instance_initiated_shutdown_behavior should be set to null as it's also not allowed in the Launch Template when used for an EC2 Auto Scaling group

references

https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html

Support AWS Provider V5 @​max-lobur (#​116)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

---

🤖 Automatic Updates

chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.35.0 (main) @renovate (#21)

This PR contains the following updates:

Package	Type	Update	Change
cloudposse/ec2-autoscale-group/aws (source)	module	minor	0.34.2 -> 0.35.0

---

Release Notes

cloudposse/terraform-aws-ec2-autoscale-group (cloudposse/ec2-autoscale-group/aws)

v0.35.0

Compare Source

Made spot_options in instance_market_options optional @​skjensen (#​117)

what

Made spot_options in instance_market_options optional.

why

On the AWS Web console there is an option to tick a box that provides guidance on how to create a Launch Template, there works with an EC2 Auto scaling group.

Expanding the "Advanced details" ticking "Request spot instance" you will see most of the options are marked as "Don't include in launch template (recommended)"

Expiry date and Interruption behaviour are not applicable. Having all spot_options as required in this template makes it impossible to enable spot instances in an EC2 Auto Scaling group.

On a related note, but not requiring any change to the module.
The variable instance_initiated_shutdown_behavior should be set to null as it's also not allowed in the Launch Template when used for an EC2 Auto Scaling group

references

https://docs.aws.amazon.com/autoscaling/ec2/userguide/create-launch-template.html

Support AWS Provider V5 @​max-lobur (#​116)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

---

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

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

Support AWS Provider V5 @max-lobur (#16)

what

Support AWS Provider V5
Linter fixes

why

Maintenance

references

https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0

Sync github @max-lobur (#13)

Sync github from the template

v0.3.1

🚀 Enhancements

fix: missing "type" in multiple attribute names @esolitos (#11)

what

Adds the missing _type suffix in the following properties:

• In block_device_mappings the attribute volume_ becomes volume_type
• In instance_market_options the attribute market_ becomes market_type
• In instance_market_options the attribute spot_instance_ becomes spot_instance_type

why

Fixes a bug where it is not possible setting up an ec2-autoscale-group with the described options.

references

fixes #6

v0.3.0

Add update_default_version parameter @ragumix (#8)

what

• Add update_default_version parameter

why

• Due to the parameter update_default_version is being used in the module terraform-aws-ec2-autoscale-group, it's better to have a possibility to overwrite default value for this parameter.

references

• https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/blob/0.31.1/variables.tf#L60-L64