deploy = true on Stack not triggering automatic deployment after Resource Sync via webhook

[ermos]

Hi there! 👋

First of all, thanks for the amazing work on Komodo - it's been great to use so far!

I have a Resource Sync configured to manage my stacks via a Git repository. When I push changes to GitHub, the webhook triggers correctly and the sync updates the stack configuration (tags, compose file changes are detected and visible on the ui). However, despite having deploy = true set on my stack, the deployment does not happen automatically. I have to manually click "Redeploy" or "Check" button on each updated stack in the UI.

Is deploy = true supposed to auto-deploy when triggered via the Execute Sync webhook? Or is manual confirmation always required? If manual confirmation is by design, is there a way to enable fully automatic deployments via Resource Sync?

Current behavior:

• Webhook is received (HTTP 200 response)
• Resource Sync runs and detects changes
• Stack tags are updated correctly
• But the deploy action is not executed automatically - it waits for manual confirmation

Expected behavior:

• With deploy = true, the stack should be automatically redeployed when the sync detects relevant changes (like compose.yaml modifications)

Configuration:

Resource Sync TOML:

[[resource_sync]]
name = "infra"
[resource_sync.config]
repo = "xxx/infra"
git_account = "xxx"
webhook_secret = "xxx"
resource_path = ["stacks", "variables.toml"]
include_variables = true

Stack TOML:

[[stack]]
tags = ["sha:31d5624"]
name = "service-a"
description = "xxx"
deploy = true

[stack.config]
server = "local"
run_directory = "stacks/service-a"
git_account = "xxx"
repo = "xxx/infra"
branch = "main"
send_alerts = false
auto_pull = true
auto_update = true
poll_for_updates = true
destroy_before_deploy = true
environment = """
....
..."""

What I've verified:

• Using the "Webhook Url - Execute Sync" (not Refresh)
• GitHub webhook returns 200
• webhook_enabled = true is set in the sync config
• deploy = true is set at the stack root level (not inside [stack.config])
• Tags are being updated on each push, confirming the sync works
• Komodo Core logs show no errors related to webhooks

Environment:

• Komodo version: v2.0.0-dev-112

Thanks in advance for your help! 🙏

[mbecker20]

What does the Run Sync update logs show? I'm not sure I can see a reason why it would do the deploy if you call the api manually via frontend vs the webhook listener calling it. For example you should see an Run Sync Update log by "Webhook User" when the webhooks calls (like when the Tags are updated), vs your username when you call "manually" from the UI. You should be seeing both of these and if you don't then maybe the webhook isn't actually triggering. You click on what is shown in screenshot to see the full logs.

[EoinFarrell]

deploy is not a field on the Stack object, see: https://docs.rs/komodo_client/latest/komodo_client/entities/stack/type.Stack.html or source code: https://github.com/moghtech/komodo/blob/main/client/core/rs/src/entities/stack.rs.
I'm looking into auto deploy's myself at the moment and it seems like a webhook call for each stack may be the cleanest if a bit cumbersome to setup

[mbunkus]

I can confirm the behavior @ermos described in their first post & would very much like to echo the need for some way to auto-trigger a redeployment of changed stacks after a resource sync — without the need for calling a huge number of webhooks afterwards. I know there's the DeployStackIfChanged function you can run via a procedure, so maybe a way to auto-trigger a procedure when a sync finishes would be a good & flexible way.

My use case is trying to do a simple git-ops thingie:

• store resource definitions in a git repo
• push to my Forgejo server
• have that trigger webhook in Komodo
• have Komodo auto-pull (sync) changes in resource definitions and re-deploy all stacks whose definitions have changed

[mbunkus]

Unfortunately DeployStackIfChanged & its batch variant do not work correctly with UI-defined compose files, for which there's #944 already. Therefore if you want to implement something based on it consider using git-repo defined stacks instead of UI defined ones (this matches better with my own use case anyway).

[mbecker20]

@mbunkus resource sync deploy = true does work, I use it

[mbunkus]

@mbecker20 I'm somewhat confused what you refer to. I do not see any setting referring to deploying in a resource sync configuration, neither in the 2.1.1 web UI nor in the model description. I've even cloned the source code & ripgrepped -i 'sync.*deploy' & looked through the results but no match stood out to me.

Can you please be more specific? It's entirely possible that I'm missing something in my config, or that I've only hit on #944 during my tests as I'm still converting from UI-defined to git-defined.

Thanks.

[mbecker20]

@mbunkus I am referring to Resource Sync deploy feature. It actually the name of the issue you commented on and is exactly the feature which "auto-trigger a redeployment of changed stacks after a resource sync". https://komo.do/docs/automate/sync-resources#stack

[jimsimon]

I've just run into this as well and it was quite frustrating to figure out what was happening. The sync ran, my stack updated, but the updated compose file was never deployed. I think this is because the sync process is only watching the toml file for changes and not anything else. So the deploy is skipped if you have a change that only touches compose.yml.

Edit: In my case, I was fixing a few stacks, one of which was just fixing an env var value in a compose file. I pushed my change to main, saw komodo run the sync, saw several stacks update, but the stack with just the env var update didn't deploy.