jaggar/iac-cljs-configs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Add note to deployment for now

Browse Source
This commit is contained in:
GigiaJ
2025-10-05 04:59:53 -05:00
parent 64857db7a5
commit 8ad1d116c8
1 changed files with 9 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
iac/src/main/deployments.cljs
View File

@@ -5,7 +5,9 @@
[base :as base] [base :as base]
[infra.dns :as dns] [infra.dns :as dns]
[k8s.services.nextcloud.service :as nextcloud-service] [k8s.services.nextcloud.service :as nextcloud-service]
[k8s.services.mesite.service :as mesite-service])) [k8s.services.mesite.service :as mesite-service]
;; [k8s.services.productive.service :as productive-service]
))
(defn app-list [stack-ref config provider] (defn app-list [stack-ref config provider]
@@ -14,9 +16,12 @@
(clj->js {:address (.getOutput stack-ref "vaultAddress") (clj->js {:address (.getOutput stack-ref "vaultAddress")
:token (.getOutput stack-ref "vaultToken")})) :token (.getOutput stack-ref "vaultToken")}))
cloudflare-result (dns/setup-dns config vault-provider) cloudflare-result (dns/setup-dns config vault-provider)
nextcloud-result (nextcloud-service/deploy provider vault-provider) ;; Manually make the namespaces and pass them
mesite-result (mesite-service/deploy provider vault-provider)] ;; You could return a map with the namespace and the resource function
{:nextcloud nextcloud-result ;; Then we can make the namespaces here and still dynamically build the resources
;; It is the cleanest and most straight forward implementation.
]
{
:cloudflare cloudflare-result})) :cloudflare cloudflare-result}))
(defn extended-exports [init] (defn extended-exports [init]