ALB Listener Priority

[ghost]

This issue was originally opened by @aaron-ballard-530 as hashicorp/terraform#18230. It was migrated here as a result of the provider split. The original body of the issue is below.

---

The documentation says that the variable Priority is optional when creating a ALB Listener Rule. However if it's excluded an error is thrown.

Terraform Version

Terraform v0.11.7
+ provider.aws v1.9.0
...

Terraform Configuration Files

...

Debug Output

Crash Output

Expected Behavior

The priority would be set to the next highest value.

Actual Behavior

An error is produced

Steps to Reproduce

Declare the resource:

resource "aws_lb_target_group" "this"
{
name = "test"
port = 443
protocol = "HTTPS"
vpc_id = "${var.vpc_id}"
health_check {
interval = 5
path = "/check"
port = 443
protocol = "HTTPS"
timeout = 3
healthy_threshold = 3
unhealthy_threshold = 5
matcher = "200"
}
}

resource "aws_lb_listener_rule" "this"
{
listener_arn = "${var.listener_arn}"
action {
type = "forward"
target_group_arn = "${aws_lb_target_group.this.arn}"
}

condition {
	field = "path-pattern"
	values = ["/test/*"]
}

}

terraform init
terraform apply

Additional Context

References

[bflad]

Hi @aaron-ballard-530 👋 Sorry you ran into unexpected behavior here. Our provider documentation is only truly valid for the current version of the provider.

The priority argument was made optional in #3219 and released in version 1.10.0 of the AWS provider. It has been available in all releases since. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

We have a backlog item to address version-specific documentation and I'll add this as a reference issue to that backlog item.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!