Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
~ update in-place
Terraform will perform the following actions:
module.this.module.nlb_internal.aws_lb.this[0] will be updated in-place
~ resource "aws_lb" "this" {
id = "arn:aws:elasticloadbalancing:eu-west-1:***:loadbalancer/net/dev-nlb-internal/f498a7274cde294e"
name = "dev-nlb-internal"
~ subnets = [
### Debug Output
_No response_
### Panic Output
_No response_
### Important Factoids
_No response_
### References
_No response_
### Would you like to implement a fix?
None
Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.
Volunteering to Work on This Issue
If you are interested in working on this issue, please leave a comment.
If this would be your first contribution, please review the contribution guide.
Terraform Core Version
1.9.8
AWS Provider Version
5.74.0
Affected Resource(s)
aws_lb
Expected Behavior
NLB to be updated successfully from using
subnets
tosubnet_mapping
attributes.Actual Behavior
Throws an error from AWS.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Initial with
subnets
:Change with private IP addresses (using
subnet_mapping
):Steps to Reproduce
subnets
(see above snippet).subnet_mapping
.Terraform will perform the following actions:
module.this.module.nlb_internal.aws_lb.this[0] will be updated in-place
~ resource "aws_lb" "this" { id = "arn:aws:elasticloadbalancing:eu-west-1:***:loadbalancer/net/dev-nlb-internal/f498a7274cde294e" name = "dev-nlb-internal" ~ subnets = [
"subnet-0aaee8ec31694627a", ] -> (known after apply) tags = { "Name" = "dev-nlb-internal" }
(17 unchanged attributes hidden)
(4 unchanged attributes hidden)
(4 unchanged attributes hidden)
(2 unchanged attributes hidden)
(2 unchanged attributes hidden)
outpost_id = (known after apply) }
}
Plan: 0 to add, 1 to change, 0 to destroy.