From f182b54bafc821e9b750e79d0823fe9adebe09e1 Mon Sep 17 00:00:00 2001
From: Rich Evans <86021670+ndc-rkevans@users.noreply.github.com>
Date: Mon, 8 Jan 2024 09:51:57 -0500
Subject: [PATCH] update haproxy.cfg to use a specific pem file

Users with proper certs will now need to name their proper cert "meza.pem"
---
 src/roles/haproxy/templates/haproxy.cfg.j2 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/roles/haproxy/templates/haproxy.cfg.j2 b/src/roles/haproxy/templates/haproxy.cfg.j2
index 2db1f0e2..38039b09 100644
--- a/src/roles/haproxy/templates/haproxy.cfg.j2
+++ b/src/roles/haproxy/templates/haproxy.cfg.j2
@@ -65,7 +65,7 @@ frontend www-http
 	default_backend www-backend
 
 frontend www-https
-	bind *:443 ssl crt /etc/haproxy/certs/
+	bind *:443 ssl crt /etc/haproxy/certs/meza.pem
 	reqadd X-Forwarded-Proto:\ https
 
 	# Keep letsencrypt stuff here for now. Probably add it back later.