From e9f5827ca9e7545ead575c8781766e4aece4f5f0 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]" <github-actions[bot]@users.noreply.github.com>
Date: Mon, 27 Mar 2023 23:06:25 +0000
Subject: [PATCH] Add deployment for PR #480

---
 staging/pr-480.yaml | 41 +++++++++++++++++++++++++++++++++++++++++
 1 file changed, 41 insertions(+)
 create mode 100644 staging/pr-480.yaml

diff --git a/staging/pr-480.yaml b/staging/pr-480.yaml
new file mode 100644
index 000000000..9ca8a92fc
--- /dev/null
+++ b/staging/pr-480.yaml
@@ -0,0 +1,41 @@
+
+apiVersion: argoproj.io/v1alpha1
+kind: Application
+metadata:
+  name: pr-480
+  namespace: argocd
+  finalizers:
+    - resources-finalizer.argocd.argoproj.io
+spec:
+  project: default
+  source:
+    repoURL: https://github.com/TUM-Dev/navigatum.git
+    targetRevision: dependabot/cargo/server/calendar/tokio-1.27.0
+    path: deployment/k3s
+    helm:
+      version: v3
+      values: |
+        namespace: pr-480
+        tag: pr-480
+        url: pr-480.nav.tum.sexy
+        server:
+            MEILI_MASTER_KEY: MjE5MGM5MmQzZWQ0MDMzYmUyZGVjZGViM2M5MTc1NGQ2ZmFjZDg1MWYwNTk1MTI2ZDUK
+            # GITHUB_TOKEN is intentionally omitted, as this file is templated and then added to git in the deployments branch
+            # JWT_KEY is omitted, because adding it would only make sense in conjunction with GITHUB_TOKEN
+            # MEILI_MASTER_KEY being added is not a security risk, since it is a hidden service and even if exposed is heavily restricted by other network policies
+  destination:
+    server: https://kubernetes.default.svc
+    namespace: pr-480
+  syncPolicy:
+    automated:
+      selfHeal: true
+      prune: true
+    syncOptions:
+      - PrunePropagationPolicy=foreground
+      - CreateNamespace=true
+    retry:
+      limit: 2
+      backoff:
+        duration: 5s
+        factor: 2
+        maxDuration: 3m0s