We are seeing errors running bbl up on AWS with BBL v9.0.1:
bbl --debug up --lb-type=cf --lb-cert=/tmp/bbl-cert --lb-chain=/tmp/bbl-cert-chain --lb-key=/tmp/bbl-key --lb-domain=<our domain>
╷
│ Error: Reference to undeclared resource
│
│ on bbl-template.tf line 2131, in locals:
│ 2131: name_servers = "${var.parent_zone == "" ? join(",", flatten(concat(aws_route53_zone.env_dns_zone.*.name_servers, tolist([list([""])])))) : join(",", flatten(concat(data.aws_route53_zone.env_dns_zone.*.name_servers, tolist([list([""])]))))}"
│
│ A data resource "aws_route53_zone" "env_dns_zone" has not been declared in
│ the root module.
╵
╷
│ Error: Missing resource instance key
│
│ on bbl-template.tf line 2199, in resource "aws_route53_record" "iso":
│ 2199: records = ["${aws_elb.iso_router_lb.dns_name}"]
│
│ Because aws_elb.iso_router_lb has "count" set, its attributes must be
│ accessed on specific instances.
│
│ For example, to correlate with indices of a referring resource, use:
│ aws_elb.iso_router_lb[count.index]
We are seeing errors running
bbl up
on AWS with BBL v9.0.1: