mirror of
https://github.com/moghtech/komodo.git
synced 2026-03-25 01:50:54 -05:00
[Feature] Add option for auto update to target the specific service instead of the whole stack #958
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/komodo#958
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @cantchooseaname8 on GitHub (Dec 5, 2024).
With the auto update feature, it would be great to have it target the specific service that has an update. When there are multiple services in a single stack, redeploying the entire stack will cause containers to restart even if they were stopped before. Targeting the specific service will avoid this and not cause containers to start when we want to remain stopped.
Perhaps keep the default as redeploying the entire stack, but add a toggle under the auto update section to choose to only redeploy individual services when there is an update. This could be useful in certain circumstances. I have some stacks where the services are not dependent on each other so redeploying the individual services would be preferred. However, I also have some stacks where the services are completely dependent on each other to function correctly. In these cases, it would be nice to have the entire stack redeployed just to give everything a fresh start after one of the services is updated. Having the option to choose based on everyone's circumstances would be helpful.
@mattsmallman commented on GitHub (Dec 9, 2024):
+1
@mbecker20 commented on GitHub (Aug 26, 2025):
This is now the case by default. You can go back to always full stack update by enabling "Full Stack Auto Update" option.