meissa/provs
7
1
Fork 0
Code Issues Pull requests Projects Releases 12 Packages Wiki Activity

reviewed

Browse source
This commit is contained in:
jerger 2022-06-30 08:38:09 +02:00
parent 79806eefab
commit 24ff5b7c15
2 changed files with 4 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
src/main/kotlin/org/domaindrivenarchitecture/provs/server/application/Application.kt
View file

@ -4,6 +4,7 @@ import org.domaindrivenarchitecture.provs.framework.core.cli.createProvInstance
import org.domaindrivenarchitecture.provs.server.domain.ServerType
import org.domaindrivenarchitecture.provs.server.domain.k3s.K3sCliCommand
import org.domaindrivenarchitecture.provs.server.domain.k3s.provisionK3s
// TODO: jem - 2022-06-30: unused import
import org.domaindrivenarchitecture.provs.server.infrastructure.provisionServerCliConvenience
import kotlin.system.exitProcess

3
src/main/kotlin/org/domaindrivenarchitecture/provs/server/domain/k3s/K3sService.kt
View file

@ -20,12 +20,14 @@ fun Prov.provisionK3s(cli: K3sCliCommand) = task {
provisionMeissaDesktopSubmodules(cli.submodules, grafanaConfigResolved)
}
// TODO: jem - 2022-06-30: das hier ist auf der falschen Ebene - gehört doch eher in die methode unten
provisionServerCliConvenience()
}
/**
* Installs a k3s server.
*/
// TODO: jem - 2022-06-30: die überladenen methoden sind schwierig - lieber unterschiedlich benennen
fun Prov.provisionK3s(
k3sConfig: K3sConfig,
grafanaConfigResolved: GrafanaAgentConfigResolved? = null,
@ -56,6 +58,7 @@ fun Prov.provisionK3s(
}
}
// TODO: jem - 2022-06-30: warum heisst diese methode meissa?
private fun Prov.provisionMeissaDesktopSubmodules(
submodules: List<String>,
grafanaConfigResolved: GrafanaAgentConfigResolved?) = task {