-
Notifications
You must be signed in to change notification settings - Fork 80
Enable schedule instance restart #6408
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #6408 +/- ##
=======================================
Coverage 76.30% 76.30%
=======================================
Files 395 395
Lines 19821 19821
Branches 4747 4747
=======================================
Hits 15124 15124
Misses 4697 4697
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
The options appear to be mutually exclusive; does this mean a user can't have both regular restarts and automatic upgrades? It feels like it should be possible to enable both? |
|
@knolleary this was a deliberate choice, let me see if I can find it in the original isssue |
|
@knolleary I can't find it, but I'm sure it was discussed, I think with regard to the original upgrade PR as that is when the backend was done for just restarting. I can look at changing it if needed? |
|
@hardillb it feels like it should be possible to enable both. |
|
@knolleary pushed updates |
fixes #6232
Description
Allows scheduling to restart Node-RED and not apply updates
Default is to do stack update, but can be changed to just restart on same schedule.
Related Issue(s)
#6232
Checklist
flowforge.yml?FlowFuse/helmto update ConfigMap TemplateFlowFuse/CloudProjectto update values for Staging/ProductionLabels
area:migrationlabel