bbl up fails when using --lb-type concourse

Open Beginner friendly
  • Is something wrong?
#701 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
67/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
aws, go, terraform
Domain
cloud, infrastructure

Research direction

Start with the generated bbl-template.tf around line 964, where the concourse_lb_80 target group is defined, and trace how its health check is configured for --lb-type concourse. Check the AWS provider constraints and the related Terraform generation or tests. Done when bbl up with this load balancer type no longer produces the reported invalid attribute combination.

Written by the indexing model from the issue text.

Description

Error: Invalid Attribute Combination
│
│ Attribute "health_check[0].matcher" cannot be specified when "health_check[0].protocol" is "TCP".
│
│ Path: health_check[0].matcher
│
│ with aws_lb_target_group.concourse_lb_80,
│ on bbl-template.tf line 964, in resource "aws_lb_target_group" "concourse_lb_80":
│ 964: resource "aws_lb_target_group" "concourse_lb_80" {

Something changed in AWS where TCP is no longer a valid entry for the health check on the port 80 target group.

I was able to hack the bbl-terraform.tf file to switch the health check from TCP to HTTP and that got past the issue.

Dominant language
Go
Stars
181
Forks
179
Avg merge
9h 54m
Merged PRs (30d)
2

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudfoundry/bosh-bootloader

All issues in cloudfoundry/bosh-bootloader

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.