Take DOKKU_FORCE_TTY setting into account for run commands with k3s-scheduler

This commit is contained in:
Tasos Maschalidis committed 2024-12-17 19:11:01 +02:00
1 parent e8d42810e6
commit 838beb4db3
2 files changed
+2 -2

No files matched your search

+1 -1
View File
@@ -385,7 +385,7 @@ func (k KubernetesClient) ExecCommand(ctx context.Context, input ExecCommandInpu
size := t.GetSize() size := t.GetSize()
sizeQueue := t.MonitorSize(size) sizeQueue := t.MonitorSize(size)
actuallyTty := sizeQueue != nil actuallyTty := (sizeQueue != nil) || os.Getenv("DOKKU_FORCE_TTY") == "true"
if actuallyTty { if actuallyTty {
req.Param("tty", "true") req.Param("tty", "true")
+1 -1
View File
@@ -1142,7 +1142,7 @@ func TriggerSchedulerRun(scheduler string, appName string, envCount int, args []
Image: image, Image: image,
ImagePullSecrets: imagePullSecrets, ImagePullSecrets: imagePullSecrets,
ImageSourceType: imageSourceType, ImageSourceType: imageSourceType,
Interactive: attachToPod, Interactive: attachToPod || os.Getenv("DOKKU_FORCE_TTY") == "true",
Labels: labels, Labels: labels,
Namespace: namespace, Namespace: namespace,
ProcessType: processType, ProcessType: processType,