From 6593d111dd76f1bc52753b5671115754ed7a744c Mon Sep 17 00:00:00 2001
From: Dusty Mabe <dusty@dustymabe.com>
Date: Apr 29 2024 19:53:13 +0000
Subject: [PATCH 1/2] switch to using --pull=newer


This new setting is more what we want I believe.

---

diff --git a/archive-repo-manager.bu b/archive-repo-manager.bu
index d1fda71..1f780f1 100644
--- a/archive-repo-manager.bu
+++ b/archive-repo-manager.bu
@@ -103,7 +103,7 @@ storage:
           Type=oneshot
           RemainAfterExit=yes
           ExecStartPre=nm-online --timeout=30
-          ExecStart=podman build --pull-always --cache-ttl=336h  \
+          ExecStart=podman build --pull=newer --cache-ttl=336h  \
                         -t localhost/archive-repo-manager:latest \
                         https://pagure.io/releng/archive-repo-manager.git
           ExecStartPost=-podman image prune --force --filter until=400h

From 2479006354b9a7f2cd2c594e82c0d9069573666b Mon Sep 17 00:00:00 2001
From: Dusty Mabe <dusty@dustymabe.com>
Date: Apr 29 2024 19:53:19 +0000
Subject: [PATCH 2/2] switch to using a1.large instance type


The t4g.medium occasionally becomes unresponsive and I wonder if it
is because one of those instance types that have "burstable" CPU
credits. I'm thinking once we use up our quota the instance then
freezes up for some time.

Switch to a1 since it's not one of those instance types.

---

diff --git a/provisioning/main.tf b/provisioning/main.tf
index e10b903..57641a2 100644
--- a/provisioning/main.tf
+++ b/provisioning/main.tf
@@ -65,7 +65,7 @@ resource "aws_instance" "archive-repo-manager" {
     Name = "archive-repo-manager-${formatdate("YYYYMMDD", timestamp())}"
   }
   ami           = local.ami
-  instance_type = "t4g.medium"
+  instance_type = "a1.large"
   user_data     = data.ct_config.butane.rendered
   associate_public_ip_address = "true"
   vpc_security_group_ids = [aws_security_group.sg.id]