Setting default_job_timeout via instance_settings.yaml
Hello,
I am unable to set the instance-level job timeout via my
instance_settings.yaml . I created a github issue for this over the weekend (https://github.com/windmill-labs/windmill/issues/6281) . Pleae let me know if there is something wrong with my approach or if this is indeed a Windmill bug.
Thank you!GitHub
bug: Set base_url and default_job_timeout via instance_settings.yam...
Describe the bug You cannot set the base_url or default_job_timeout instance settings via pushing a instance_settings.yaml to a windmill instance. To reproduce Minimal reproducible instance_setting...
3 Replies
Hi @tl_jacob , I think what you want is a windmill operator
that check if a kube config has changed and then apply the setting in the database directly
we do not have that but that's how we would do it ideally
well actually since you're talking about the CLI here i'm mistaken, I was mentionning your weekend issue
@rubenf some context:
- we are self-hosting on ecs
- yes, the ideal workflow would be for us to be able to modify at least
default_job_timeout via the CLI (pushing an instance_settings.yaml change to our instance)