Hi @Montana,

I have this question that I am not sure how to formulate, so I was hoping you could help. To best formulate it, is me using an example. I have the following resource definition for was subnets based in an input parameter variable:

resource "aws_subnet" "monitoring_subnetwork" {
  count = length(var.monitoring_subnets)

  vpc_id     = module.vpc.vpc_id
  cidr_block = var.monitoring_subnets[count.index]

  availability_zone= "${data.aws_availability_zones.available.names[count.index % length(data.aws_availability_zones.available.names)]}"

  tags = {
    Name = "Monitoring private-1${replace(
      data.aws_availability_zones.available.names[count.index % length(data.aws_availability_zones.available.names)], 
      data.aws_availability_zones.available.id, "")}"
  }
}

I want to simplify this code to make it more readable and maintainable.

whilst working on that I noticed that the current implementation only searches for scripts with the shebang #!/usr/bin/env bash - and whilst that's the best practice shebang, it's not unknown for people to use

 #!/bin/bash
 #!/usr/bin/bash

or variants with sh instead of bash.

i'd recommend using this instead:

git grep -El '^#!/.+\b(bash|sh)\b'

(note the extended regex param)

thanks