chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.40.0 (release/v0) #124
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
0.30.0
->0.40.0
Release Notes
cloudposse/terraform-aws-ec2-autoscale-group (cloudposse/ec2-autoscale-group/aws)
v0.40.0
Compare Source
fix: Tagging @MaxymVlasov (#143)
why
var.tags
does not provide any tags if you rely oncontext
:🤖 Automatic Updates
Update .github/settings.yml @osterman (#142)
what
.github/settings.yml
.github/auto-release.yml
fileswhy
.github/settings.yml
from org levelreferences
Update .github/settings.yml @osterman (#141)
what
.github/settings.yml
.github/auto-release.yml
fileswhy
.github/settings.yml
from org levelreferences
Update release workflow to allow pull-requests: write @osterman (#140)
what
.github/workflows/release.yaml
) to have permission to comment on PRwhy
Update GitHub Workflows to use shared workflows from '.github' repo @osterman (#139)
what
.github/workflows
) to use shared workflows from.github
repowhy
chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @renovate (#131)
This PR contains the following updates:2.4.1
->2.4.2
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.2
Compare Source
🚀 Enhancements
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)
This PR contains the following updates:
1.3.0
->1.4.0
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0
Compare Source
Add il-central-1 region @​&#​8203;jasonmk (#&#​8203;31)
what
Add new Tel Aviv (il-central-1) region
why
Provide full coverage
references
Sync github @​&#​8203;max-lobur (#&#​8203;27)
Rebuild github dir from the template
🤖 Automatic Updates
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)
This PR contains the following updates:
1.3.0
->1.4.0
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0
Compare Source
Add il-central-1 region @​&#​8203;jasonmk (#&#​8203;31)
what
Add new Tel Aviv (il-central-1) region
why
Provide full coverage
references
Sync github @​&#​8203;max-lobur (#&#​8203;27)
Rebuild github dir from the template
Update README.md and docs @​cloudpossebot (#​189)
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
Update GitHub Workflows to Fix ReviewDog TFLint Action @osterman (#138)
what
.github/workflows
) to addissue: write
permission needed by ReviewDogtflint
actionwhy
Update GitHub workflows @osterman (#137)
what
.github/workflows/settings.yaml
)why
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#136)
what
why
cldouposse/.github
repositoryAdd GitHub Settings @osterman (#135)
what
.github/settings.yaml
)why
Update README.md and docs @cloudpossebot (#132)
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
Update Scaffolding @osterman (#133)
what
make readme
to rebuildREADME.md
fromREADME.yaml
why
.github
repochore(deps): update terraform cloudposse/vpc/aws to v2.2.0 @renovate (#130)
This PR contains the following updates:2.1.1
->2.2.0
Release Notes
cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)
v2.2.0
Compare Source
Update README.md and docs @cloudpossebot (#129)
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
chore(deps): update terraform cloudposse/vpc/aws to v2.1.1 @renovate (#128)
This PR contains the following updates:2.1.0
->2.1.1
Release Notes
cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)
v2.1.1
Compare Source
Add support for network address usage metrics @​lanzrein (#​124)
what
This PR adds support for Network Address Usage Metrics on the VPC.
AWS documentation : https://docs.aws.amazon.com/vpc/latest/userguide/network-address-usage.html
Terraform documentation : https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/vpc#enable_network_address_usage_metrics
why
Network Address Usage metrics can help monitor the growth of a VPC and would be useful for any user.
Enable this after creating a VPC does not trigger recreation of the VPC.
references
closes #115
Sync github @​max-lobur (#​120)
Rebuild github dir from the template
🤖 Automatic Updates
Update README.md and docs @​cloudpossebot (#​125)
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.39.0
Compare Source
Change mixed instances policy fields to optional @pagmerek (#126)
what
why
In my other PR for terraform ECS component I changed the default value of variable that is being passed here. Without this change terraform will complain that there is no such field as instances_distribution/override
references
v0.38.0
Compare Source
🚀 Enhancements
Add optional network_interface_id variable @gbarna-bd (#124)
what
network_interface_id
variable to launch_templatewhy
references
v0.37.2
Compare Source
🚀 Enhancements
Require AWS provider 5.16+ @raymondchen625 (#123)
what
Version
v0.36.0
does not work with AWS Provider 4.X.why
In PR #121 of
v0.36.0
, the preference keyscale_in_protected_instances
, which had been available only since AWS Provider5.16.0
introduced by PR#33310, was added. That basically upgrades the required AWS provider version to5.16.0+
.We will get errors like the below while planning with AWS provider
<5.16.0
:references
🐛 Bug Fixes
Require AWS provider 5.16+ @raymondchen625 (#123)
what
Version
v0.36.0
does not work with AWS Provider 4.X.why
In PR #121 of
v0.36.0
, the preference keyscale_in_protected_instances
, which had been available only since AWS Provider5.16.0
introduced by PR#33310, was added. That basically upgrades the required AWS provider version to5.16.0+
.We will get errors like the below while planning with AWS provider
<5.16.0
:references
v0.37.1
Compare Source
fix: block_device_mappings required optional fields @MaxymVlasov (#127)
what
Fix 0.37.0
why
As per the code in main.tf, all these stuff are optional
https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/blob/b757eb9037b9eae3235522800530117e66d535b2/main.tf#L6-L24
references
https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/pull/97
🤖 Automatic Updates
Update Terraform cloudposse/dynamic-subnets/aws to v2.4.1 @renovate (#125)
This PR contains the following updates:
2.3.0
->2.4.1
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.1
Compare Source
🚀 Enhancements
Add subnet ARNs to outputs @​Nuru (#​188)
what
why
v2.4.0
Compare Source
Update dependencies, remove deprecation, add NACL example @​Nuru (#​184)
Note
Dropping support for deprecated EC2-Classic
With this release, EIPs allocated for NAT ingress are allocated in the default domain. This most likely does not affect you, but for accounts created before 2013-12-04 (almost 10 years ago as of this writing), the default domain could be EC2-Classic rather than the current VPC. Previously this module forced the EIPs to be in the VPC domain, but the breaking changes between AWS Provider v4 and v5 make that difficult.
If you find yourself in the rare situation where the EIPs allocated by this module are in EC2-Classic but you want them in VPC, then create the EIPs outside of this module and supply them to this module via
nat_elastic_ips
.Custom NACLs
This release includes an example (
examples/nacls/
) showing how to create custom NACLs in conjunction with this module. Note that by default, this module creates wide-open NACLs, and subnets can only have one NACL associated with them. If you try to add a NACL to a subnet without disabling the default NACLs, you may get a possibly confusing error like:See https://github.com/hashicorp/terraform-provider-aws/issues/31888
what
null
as meaning "default")aws_eip
vpc = true
why
references
v0.37.0
Compare Source
* add throughput to block_device_mapping @zaksamalik (#97)
what
throughput
toblock_device_mapping
why
throughput
configuration for block device mappingsreferences
v0.36.0
Compare Source
🚀 Enhancements
Fix: instance refresh missing properties @ebarriosjr (#121)
what
This PR adds two missing properties to the instance_refresh stanza.
why
Right now there is no way to configure scale_in_protected_instances and standby_instances in the instance refresh stanza.
references
This solves: #120
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#122)
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.35.1
Compare Source
add instance refresh preferences @scott-doyland-burrows (#115)
what
Adds
skip_matching
andauto_rollback
to the instance refresh preferences.Allows the instance refresh preferences to be optional. If the values are not set in the calling module, then the default values are used as per:
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#instance_refresh
why
Previously it was not possible to set the
skip_matching
andauto_rollback
.It was also not possible to omit preferences from the calling module and just use the defaults instead.
With this change we can now set preferences and/or omit preferences that we wish to use the defaults for.
The change should not cause any diffs in current infrastructure.
references
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/autoscaling_group#instance_refresh
examples
It is now possible to use something such as this to use defaults:
or this to override certain defaults:
🤖 Automatic Updates
Update README.md and docs @cloudpossebot (#119)
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.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 groupreferences
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
v0.34.2
Compare Source
🐛 Bug Fixes
Restore tags output @Nuru (#114)
what
autoscaling_group_tags
output removed in #113why
v0.34.1
Compare Source
Sync github @max-lobur (#110)
Rebuild github dir from the template
🚀 Enhancements
Support AWS Provider V5 @max-lobur (#113)
what
why
resource/aws_autoscaling_group: Remove deprecated tags attribute (https://github.com/hashicorp/terraform-provider-aws/issues/30842)
references
https://github.com/hashicorp/terraform-provider-aws/releases/tag/v5.0.0
v0.34.0
Compare Source
v0.33.0
Compare Source
To support custom alarms with extended_statistic @linhkikuchi (#102)
what
statistic
, notextended_statistic
for custom_alarmswhy
extended_statistic
is useful for metricTargetResponseTime
references
closes #​123
, if this PR closes a GitHub issue#123
v0.32.0
Compare Source
Add support for instance reuse policy and fix bug for tag for v4 @linhkikuchi (#101)
what
why
references
v0.31.1
Compare Source
🚀 Enhancements
Use tag and deprecate tags @nitrocode (#95)
what
why
references
v0.31.0
Compare Source
Feat/instance metadata options - Updated @rwc (#94)
Full credit goes to @zen and his prior work in https://github.com/cloudposse/terraform-aws-ec2-autoscale-group/pull/88. Simply fixing up the issues @Nuru called out in order to get this over the finish line for production use.
what
why
references
git.io->cloudposse.tools update @dylanbannon (#89)
what and why
Change all references to
git.io/build-harness
intocloudposse.tools/build-harness
, sincegit.io
redirects will stop working on April 29th, 2022.References
v0.30.1
Compare Source
🚀 Enhancements
Add missing dollar sign @nitrocode (#86)
what
why
references
Chore: Run `make github/init` @korenyoni (#82)
what
make github/init
.why
references
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - 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.
This PR was generated by Mend Renovate. View the repository job log.