🤖 Automatic Updates
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#25)
## 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
chore(deps): update terraform cloudposse/stack-config/yaml to v1.8.0 @[renovate[bot]](https://github.com/apps/renovate) (#4)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/stack-config/yaml (source) | module | minor | 1.5.0 -> 1.8.0 |
Release Notes
cloudposse/terraform-yaml-stack-config (cloudposse/stack-config/yaml)
v1.8.0
: [remote-state] Improve backend compatibility
Among other things detailed below, this release enables users to fix deprecation warnings like:
│ Warning: Deprecated Parameters
│
│ with module.account_map.data.terraform_remote_state.data_source[0],
│ on .terraform/modules/account_map/modules/remote-state/data-source.tf line 88, in data "terraform_remote_state" "data_source":
│ 88: data "terraform_remote_state" "data_source" {
│
│ The following parameters have been deprecated. Replace them as follows:
│ * role_arn -> assume_role.role_arn
If you are receiving deprecation warnings from remote-state, they can now be resolved by updating your backend
/remote_state_backend
configuration to match the version of Terraform or Tofu you are using. For example, change
terraform:
backend:
s3:
bucket: my-tfstate-bucket
dynamodb_table: my-tfstate-lock-table
role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-role
remote_state_backend:
s3:
role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-read-only-role
to
terraform:
backend:
s3:
bucket: my-tfstate-bucket
dynamodb_table: my-tfstate-lock-table
assume_role:
role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-role
remote_state_backend:
s3:
assume_role:
role_arn: arn:aws:iam::123456789012:role/my-tfstate-access-read-only-role
🚀 Enhancements
[remote-state] Improve backend compatibility @Nuru (#105)
what
- Improve remote-state backend compatibility
Rather than trying to parse the backend configuration, as a general rule we now just pass it through to the data source. This provides future-proof compatibility with all backends supported by Terraform and OpenTofu.
why
- This prevents the need for updates like #99 to provide configuration for future S3 backends, while eliminating compatibility issues like #102.
- This also eliminates deprecation warnings caused by forcing configuration to look a certain way.
- Now, users can manage their own remote state configuration to match their toolset.
references
- Closes #102
v1.7.0
: (not recommended)
feat: support for gcs backends @burnzy (#95)
what
Simple change to add support for GCS backends
why
Allows GCP users (users with gcs backends) to make use of this remote-state module for sharing data between components.
references
🚀 Enhancements
Support local backend @Nuru (#104)
what
- Support retrieving remote state from local backends
- NOTE: Using relative paths in local backends is tricky, because the path needs to resolve to the same directory from the source root module directory as from the client root module directory.
- Fix Terratests
- The
spacelift
test suite is broken, and we never previously required it to work, so it is now skipped
- The
- Update test suite to use
go
v1.21 and update dependencies
why
🤖 Automatic Updates
Bump the go_modules group in /test/src with 5 updates @dependabot (#94)
Bumps the go_modules group in /test/src with 5 updates:Package | From | To |
---|---|---|
github.com/hashicorp/go-getter | 1.7.1 |
1.7.5 |
golang.org/x/crypto | 0.1.0 |
0.17.0 |
golang.org/x/net | 0.8.0 |
0.10.0 |
google.golang.org/grpc | 1.51.0 |
1.56.3 |
google.golang.org/protobuf | 1.28.1 |
1.30.0 |
Updates github.com/hashicorp/go-getter
from 1.7.1 to 1.7.5
Release notes
Sourced from github.com/hashicorp/go-getter's releases.
v1.7.5
What's Changed
- Prevent Git Config Alteration on Git Update by
@dduzgun-security
in hashicorp/go-getter#497New Contributors
@dduzgun-security
made their first contribution in hashicorp/go-getter#497Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.4...v1.7.5
v1.7.4
What's Changed
- Escape user-provided strings in
git
commands hashicorp/go-getter#483- Fixed a bug in
.netrc
handling if the file does not exist hashicorp/go-getter#433Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.3...v1.7.4
v1.7.3
What's Changed
- SEC-090: Automated trusted workflow pinning (2023-04-21) by
@hashicorp-tsccr
in hashicorp/go-getter#432- SEC-090: Automated trusted workflow pinning (2023-09-11) by
@hashicorp-tsccr
in hashicorp/go-getter#454- SEC-090: Automated trusted workflow pinning (2023-09-18) by
@hashicorp-tsccr
in hashicorp/go-getter#458- don't change GIT_SSH_COMMAND when there is no sshKeyFile by
@jbardin
in hashicorp/go-getter#459New Contributors
@hashicorp-tsccr
made their first contribution in hashicorp/go-getter#432Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.2...v1.7.3
v1.7.2
What's Changed
- Don't override
GIT_SSH_COMMAND
when not needed by@nl-brett-stime
hashicorp/go-getter#300Full Changelog: https://github.com/hashicorp/go-getter/compare/v1.7.1...v1.7.2
Commits
5a63fd9
Merge pull request #497 from hashicorp/fix-git-update5b7ec5f
fetch tags on update and fix tests9906874
recreate git config during update to prevent config alteration268c11c
escape user provide string to git (#483)975961f
Merge pull request #433 from adrian-bl/netrc-fix0298a22
Merge pull request #459 from hashicorp/jbardin/setup-git-envc70d9c9
don't change GIT_SSH_COMMAND if there's no keyfile3d5770f
Merge pull request #458 from hashicorp/tsccr-auto-pinning/trusted/2023-09-180688979
Result of tsccr-helper -log-level=info -pin-all-workflows .e66f244
Merge pull request #454 from hashicorp/tsccr-auto-pinning/trusted/2023-09-11- Additional commits viewable in compare view
Updates golang.org/x/crypto
from 0.1.0 to 0.17.0
Commits
9d2ee97
ssh: implement strict KEX protocol changes4e5a261
ssh: close net.Conn on all NewServerConn errors152cdb1
x509roots/fallback: update bundlefdfe1f8
ssh: defer channel window adjustmentb8ffc16
blake2b: drop Go 1.6, Go 1.8 compatibility7e6fbd8
ssh: wrap errors from client handshakebda2f3f
argon2: avoid clobbering BP325b735
ssh/test: skip TestSSHCLIAuth on Windows1eadac5
go.mod: update golang.org/x dependenciesb2d7c26
ssh: add (*Client).DialContext method- Additional commits viewable in compare view
Updates golang.org/x/net
from 0.8.0 to 0.10.0
Commits
daac0ce
go.mod: update golang.org/x dependencies82780d6
http2: don't reuse connections that are experiencing errors0bfab66
ipv4, ipv6: drop redundant skip checks based on GOOS938ff15
ipv4, ipv6, nettest: skip unsupported tests on wasip1eb1572c
html: another shot at security doc9001ca7
nettest: re-enable unixpacket tests on netbsd/3863d5a8ee
internal/socks: permit authenticating with an empty password694cff8
go.mod: update golang.org/x dependencies6960703
http2: log the correct error when retrying in (*Transport).RoundTripOpt9f24bb4
http2: properly discard data received after request/response body is closed- Additional commits viewable in compare view
Updates google.golang.org/grpc
from 1.51.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 withcodes.Unknown
when the error implements theGRPCStatus()
method, and callingGRPCStatus()
returnsnil
. (#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 withcodes.Unknown
when the error implements theGRPCStatus()
method, and callingGRPCStatus()
returnsnil
. (#6374)Release 1.55.0
Behavior Changes
... (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.56.3-dev (#6434)faab873
Update version.go to v1.56.2 (#6432)6b0b291
status: fix panic when servers return a wrapped error with status OK (#6374) ...ed56401
[PSM interop] Don't fail target if sub-target already failed (#6390) (#6405)cd6a794
Update version.go to v1.56.2-dev (#6387)5b67e5e
Update version.go to v1.56.1 (#6386)d0f5150
client: handle empty address lists correctly in addrConn.updateAddrs (#6354) ...997c1ea
Change version to 1.56.1-dev (#6345)- Additional commits viewable in compare view
Updates google.golang.org/protobuf
from 1.28.1 to 1.30.0
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase
.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditions
will show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major version
will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor version
will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>
will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>
will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>
will remove the ignore condition of the specified dependency and ignore conditions
You can disable automated security fix PRs for this repo from the Security Alerts page.
Migrate new test account @osterman (#103)
what
- Update
.github/settings.yml
- Update
.github/chatops.yml
files
why
- Re-apply
.github/settings.yml
from org level to getterratest
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 (#101)
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 (#100)
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
v1.6.0
: (not recommended)
NOTE: Requires Terraform v1.6.4 or later to work with S3 backends. See #102
what
Add options required by S3-compatible backend for Oracle Cloud Infrastructure as described here
why
Some of the options available for S3 backend for Terraform are not supported by remote-state module. However, they are useful when working with cloud providers other than AWS.
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.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
chore(deps): update terraform cloudposse/ec2-autoscale-group/aws to v0.41.0 @[renovate[bot]](https://github.com/apps/renovate) (#3)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/ec2-autoscale-group/aws (source) | module | minor | 0.35.1 -> 0.41.0 |
Release Notes
cloudposse/terraform-aws-ec2-autoscale-group (cloudposse/ec2-autoscale-group/aws)
v0.41.0
add max_healthy_percentage - option used during instance refresh @scott-doyland-burrows (#149)
what
This is adding the max_healthy_percentage
option.
This allows the instance refresh to set this value.
min_healthy_percentage
is already set as an option.
why
The option is currently missing from the terraform module.
references
fix: Terratest Account ID @milldr (#150)
what
- Remove old account ID check from tests
why
- Account ID has changed. We shouldnt use the account ID to check
references
🤖 Automatic Updates
Migrate new test account @osterman (#148)
what
- Update
.github/settings.yml
- Update
.github/chatops.yml
files
why
- Re-apply
.github/settings.yml
from org level to getterratest
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 (#147)
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 (#146)
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 (#145)
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
v0.40.0
fix: Tagging @MaxymVlasov (#143)
why
var.tags
does not provide any tags if you rely on context
:
module {
...
context = module.this.context
}
🤖 Automatic Updates
Update .github/settings.yml @osterman (#142)
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 (#141)
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 (#140)
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 (#139)
what
- Update workflows (
.github/workflows
) to use shared workflows from.github
repo
why
- Reduce nested levels of reusable workflows
chore(deps): update terraform cloudposse/dynamic-subnets/aws to v2.4.2 @renovate (#131)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/dynamic-subnets/aws (source) | module | patch | 2.4.1 -> 2.4.2 |
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.2
🚀 Enhancements
chore(deps): update terraform cloudposse/utils/aws to v1.4.0 (main) @​renovate (#​191)
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/utils/aws (source) | module | minor | 1.3.0 -> 1.4.0 |
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0
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:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/utils/aws (source) | module | minor | 1.3.0 -> 1.4.0 |
Release Notes
cloudposse/terraform-aws-utils (cloudposse/utils/aws)
v1.4.0
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
- Update workflows (
.github/workflows
) to addissue: write
permission needed by ReviewDogtflint
action
why
- The ReviewDog action will comment with line-level suggestions based on linting failures
Update GitHub workflows @osterman (#137)
what
- Update workflows (
.github/workflows/settings.yaml
)
why
- Support new readme generation workflow.
- Generate banners
Use GitHub Action Workflows from `cloudposse/.github` Repo @osterman (#136)
what
- Install latest GitHub Action Workflows
why
- Use shared workflows from
cldouposse/.github
repository - Simplify management of workflows from centralized hub of configuration
Add GitHub Settings @osterman (#135)
what
- Install a repository config (
.github/settings.yaml
)
why
- Programmatically manage GitHub repo settings
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
- Reran
make readme
to rebuildREADME.md
fromREADME.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
chore(deps): update terraform cloudposse/vpc/aws to v2.2.0 @renovate (#130)
This PR contains the following updates:Package | Type | Update | Change |
---|---|---|---|
cloudposse/vpc/aws (source) | module | minor | 2.1.1 -> 2.2.0 |
Release Notes
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:Package | Type | Update | Change |
---|---|---|---|
cloudposse/vpc/aws (source) | module | patch | 2.1.0 -> 2.1.1 |
Release Notes
cloudposse/terraform-aws-vpc (cloudposse/vpc/aws)
v2.1.1
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
Change mixed instances policy fields to optional @pagmerek (#126)
what
- change variable field of mixed_instances_policy to optional
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
NOTE: This PR must be merged first and then I will change version of ASG component in ECS component
v0.38.0
🚀 Enhancements
Add optional network_interface_id variable @gbarna-bd (#124)
what
- Add optional
network_interface_id
variable to launch_template
why
- Allow the attaching of existing network interfaces
references
v0.37.2
🚀 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 key scale_in_protected_instances
, which had been available only since AWS Provider 5.16.0
introduced by PR#33310, was added. That basically upgrades the required AWS provider version to 5.16.0+
.
We will get errors like the below while planning with AWS provider <5.16.0
:
│ Error: Unsupported argument
│
│ on .terraform/modules/autoscale_group/main.tf line 187, in resource "aws_autoscaling_group" "default":
│ 187: scale_in_protected_instances = lookup(preferences.value, "scale_in_protected_instances", null)
│
│ An argument named "scale_in_protected_instances" is not expected here.
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 key scale_in_protected_instances
, which had been available only since AWS Provider 5.16.0
introduced by PR#33310, was added. That basically upgrades the required AWS provider version to 5.16.0+
.
We will get errors like the below while planning with AWS provider <5.16.0
:
│ Error: Unsupported argument
│
│ on .terraform/modules/autoscale_group/main.tf line 187, in resource "aws_autoscaling_group" "default":
│ 187: scale_in_protected_instances = lookup(preferences.value, "scale_in_protected_instances", null)
│
│ An argument named "scale_in_protected_instances" is not expected here.
references
v0.37.1
fix: block_device_mappings required optional fields @MaxymVlasov (#127)
what
Fix 0.37.0
│ Error: Invalid value for input variable
│
│ on main.tf line 125, in module "autoscale_group":
│ 125: block_device_mappings = var.block_device_mappings
│
│ The given value is not suitable for
│ module.autoscale_group.var.block_device_mappings declared at
│ .terraform/modules/autoscale_group/variables.tf:72,1-33: incorrect list
│ element type: attribute "ebs": attribute "throughput" is required.
╵
why
As per the code in main.tf, all these stuff are optional
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:
Package | Type | Update | Change |
---|---|---|---|
cloudposse/dynamic-subnets/aws (source) | module | minor | 2.3.0 -> 2.4.1 |
Release Notes
cloudposse/terraform-aws-dynamic-subnets (cloudposse/dynamic-subnets/aws)
v2.4.1
🚀 Enhancements
Add subnet ARNs to outputs @​Nuru (#​188)
what
- Add subnet ARNs to outputs
why
- Closes #171
v2.4.0
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:
│ Error: creating EC2 Network ACL: creating EC2 Network ACL (acl-0376c5f12dd9d784d) Association: InvalidAssociationID.NotFound: The association ID 'aclassoc-0818d5a9e3876a2bb' does not exist
See https://github.com/hashicorp/terraform-provider-aws/issues/31888
what
- Make appropriate inputs non-nullable (treat an input of
null
as meaning "default") - Remove
aws_eip
vpc = true
- Update terraform cloudposse/utils/aws to v1.3.0 (Supersedes and closes #182)
- Add example of how to add custom NACLs to subnets created by this module (Supersedes and closes #176)
- Update tests and test framework
why
- Allow better, more consistent configuration
- Deprecated
- Include support for new AWS regions
- Encourage composition of modules and resources rather than aggregation of functionality into bloated modules (c.f. #176)
- Stay current with features, bug fixes, and security updates
references
- Terraform AWS Provider Version 5 Upgrade Guide: aws_eip
- Disallowing Null Input Values
- EC2 Classic
v0.37.0
* add throughput to block_device_mapping @zaksamalik (#97)
what
- add
throughput
toblock_device_mapping
why
- allows
throughput
configuration for block device mappings
references
- closes #96
v0.36.0
🚀 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
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.
- If you want to rebase/retry this PR, check this box
This PR was generated by Mend Renovate. View the repository job log.
Enable merge queue @goruha (#24)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
Enable merge queue @goruha (#23)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
Enable merge queue @goruha (#22)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
Enable merge queue @goruha (#21)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
Enable merge queue @goruha (#20)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
Enable merge queue @goruha (#19)
## what - Added `auto-merge` workflow - Update `settings.yaml` - Fix CodeOwners fileswhy
- Support auto merge PRs
- Create merge queue
- Implement new CodeOwners policy
Update README.md and docs @[cloudposse-releaser[bot]](https://github.com/apps/cloudposse-releaser) (#18)
## 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