RB
@BGarber42 @archenroot Oh I was mistaken. You do not need a target group attachment. I believe only the listener rule (created by the `alb_ingress` module) is required as that attaches...
I just ran into this again. I'm glad this ticket was written because the above description reminded me that I do not need a specific [`aws_lb_target_group_attachment`](https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/lb_target_group_attachment). If you want to...
Perhaps we need to bump up the modules in our examples. For now, I would use the latest versions of the modules to workaround the issue.
@JoostSaanen could you fix the auto format issues. Normally the bot user would be able to do this but because the fork doesnt have give the cloudpossebot access, it needs...
Maybe the role has to be created first and then the domain policy. Perhaps an explicit depends_on may solve this issue.
@rverma-nsl if this option was added using a [`random_string`](https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/string) resource, the password would be stored in the remote state. Wouldn't it be better if the password was created outside of...
Actually, we have some art for this. We should use [`random_pet`](https://registry.terraform.io/providers/hashicorp/random/latest/docs/resources/pet) for the username and `random_string` for the password.
/test test/terratest
/test terratest