Selective redeploy, instead of wiping out whole service stacks

[pcs3rd]

Is it possible to tell doco to update compose stacks instead of redeploying?
It's wiping out stuff that doesn't change, irregardless of state.

[gitnew12]

I believe this might be a glitch. My workaround; compose down manually those stacks that keep redeploying.

[trevorswanson]

I think I'm experiencing the same thing, can you confirm if it's the same issue or if I should start my own thread?

In my doco-cd.yml I have about 10-15 stacks defined each with their own compose file, env files, etc. -- each has its own working directory

No matter which file I update, in which stack, when doco-cd receives a webhook it seems to redeploy every stack. I'd like for only the stack that was modified to be redeployed instead of everything

[pcs3rd]

It's not that doco redeploys all stacks- just that I can run 'docker compose up -d' to replace/update services that have been changed, without redeploying those that don't need updating.

So, doco-cd defaults to the '--force-redeploy' behavior, and doesn't seem to have an option to not.

[trevorswanson]

Got it, sorry. I'll start my own issue

[gitnew12]

Once you let Doco-CD take over of deployment, you shouldn't be using docker compose up manually anymore.

[pcs3rd]

I'm not. I'm describing deployment behavior (redeployment vs update).