From b73ae4bf8dbf66c70949bfa9627390fb2dacf40f Mon Sep 17 00:00:00 2001
From: Derek Horton <dehort@redhat.com>
Date: Thu, 5 Sep 2024 12:57:08 -0500
Subject: [PATCH] I think the STORAGE_MAX_CONCURRENCY setting is in the wrong
 place.  The api doesn't use it, the validator does.  No biggie, just move it,
 fix it, etc Increase the max artifact size

---
 deploy/clowdapp.yaml | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/deploy/clowdapp.yaml b/deploy/clowdapp.yaml
index 4b300f3e..e83b155b 100644
--- a/deploy/clowdapp.yaml
+++ b/deploy/clowdapp.yaml
@@ -150,9 +150,6 @@ objects:
           - name: RBAC_HOST
             value: ${RBAC_HOST}
 
-          - name: STORAGE_MAX_CONCURRENCY
-            value: ${STORAGE_MAX_CONCURRENCY}
-
           - name: TENANT_TRANSLATOR_IMPL
             value: ${TENANT_TRANSLATOR_IMPL}
           - name: TENANT_TRANSLATOR_HOST
@@ -265,6 +262,10 @@ objects:
             value: ${LOG_LEVEL}
           - name: DB_SSLMODE
             value: ${DB_SSLMODE}
+          - name: STORAGE_MAX_CONCURRENCY
+            value: ${STORAGE_MAX_CONCURRENCY}
+          - name: ARTIFACT_MAX_SIZE
+            value: ${ARTIFACT_MAX_SIZE}
         resources:
           limits:
             cpu: ${CPU_LIMIT}
@@ -341,6 +342,8 @@ parameters:
 
 - name: STORAGE_MAX_CONCURRENCY
   value: "5"
+- name: ARTIFACT_MAX_SIZE
+  value: '3145728'
 
 - name: RETURN_URL
   value: TBD