Linked Repository on Different Server Not Auto-Deploying After Webhook #591

New Issue

2025-10-31T15:16:00-05:00

GiteaMirror commented

2025-10-31 15:16:00 -05:00

Originally created by @pluusla on GitHub (Sep 21, 2025).

Issue Overview

I've noticed that when using a linked repository with stacks on different servers, auto-deployment via webhooks doesn't seem to work consistently. I'd like to understand if this is expected behavior or if I'm missing something in my configuration.

Reproduction Steps

I have two different stack configurations:

Stack 1 (Works correctly with webhooks):

toml

[[stack]]
name = "stack_a"
[stack.config]
server = "server_1"
auto_pull = false
poll_for_updates = true
auto_update = true
git_provider = "my-git-server:3000"
git_https = false
git_account = "user"
repo = "user/projects"
branch = "master"
webhook_secret = "redacted"
run_directory = "./stacks/stack_a"

toml

[[stack]]
name = "stack_b"
[stack.config]
server = "server_2"
poll_for_updates = true
auto_update = true
auto_update_all_services = true
linked_repo = "Git_Master_Repo"
webhook_secret = "redacted"
run_directory = "./stacks/stack_b"
Linked Repository Configuration:

toml

[[repo]]
name = "Git_Master_Repo"
[repo.config]
server = "server_1"
git_provider = "my-git-server:3000"
git_https = false
git_account = "user"
repo = "user/projects"
branch = "master"
path = "/etc/komodo/repos/master"
webhook_secret = "redacted"

Expected Behavior

I expected that when changes are pushed to the git repository, both stacks would auto-deploy since they both have webhooks configured with the same repository.

Actual Behavior

Stack 1 (direct git configuration) automatically deploys when changes are pushed
Stack 2 (using linked_repo) does not automatically deploy when changes are pushed, even though the webhook is configured identically

Additional Observations

Server Mismatch: The linked repository is on server_1 while Stack 2 is on server_2. I'm wondering if this is intentionally not supported?
Missing Documentation: I couldn't find clear guidance in the documentation about how webhooks should work when a linked repository and a stack are on different servers.
Server Field Requirement: I found that removing the server field from the linked repository configuration causes the pull repository task to run indefinitely without completing.

Questions

Is it by design that linked repositories cannot trigger webhook deployments on stacks located on different servers?
If it is supported, how should webhooks be configured to properly trigger deployments across different servers?
Is there a specific network configuration required for cross-server webhook propagation?
Does using a linked repository require additional configuration to enable webhook-based deployments?

Environment

Komodo version: 1.19.4
OS: Linux
Git provider: Self-hosted Git server Forgejo
Deployment method: Docker

I appreciate any insights on whether this is expected behavior or if I'm missing something in my configuration. Thank you!

Originally created by @pluusla on GitHub (Sep 21, 2025). ### Issue Overview I've noticed that when using a linked repository with stacks on different servers, auto-deployment via webhooks doesn't seem to work consistently. I'd like to understand if this is expected behavior or if I'm missing something in my configuration. ### Reproduction Steps I have two different stack configurations: Stack 1 (Works correctly with webhooks): toml ``` [[stack]] name = "stack_a" [stack.config] server = "server_1" auto_pull = false poll_for_updates = true auto_update = true git_provider = "my-git-server:3000" git_https = false git_account = "user" repo = "user/projects" branch = "master" webhook_secret = "redacted" run_directory = "./stacks/stack_a" ``` toml ``` [[stack]] name = "stack_b" [stack.config] server = "server_2" poll_for_updates = true auto_update = true auto_update_all_services = true linked_repo = "Git_Master_Repo" webhook_secret = "redacted" run_directory = "./stacks/stack_b" Linked Repository Configuration: ``` toml ``` [[repo]] name = "Git_Master_Repo" [repo.config] server = "server_1" git_provider = "my-git-server:3000" git_https = false git_account = "user" repo = "user/projects" branch = "master" path = "/etc/komodo/repos/master" webhook_secret = "redacted" ``` ### Expected Behavior I expected that when changes are pushed to the git repository, both stacks would auto-deploy since they both have webhooks configured with the same repository. ### Actual Behavior - Stack 1 (direct git configuration) automatically deploys when changes are pushed - Stack 2 (using linked_repo) does not automatically deploy when changes are pushed, even though the webhook is configured identically ### Additional Observations 1. Server Mismatch: The linked repository is on server_1 while Stack 2 is on server_2. I'm wondering if this is intentionally not supported? 2. Missing Documentation: I couldn't find clear guidance in the documentation about how webhooks should work when a linked repository and a stack are on different servers. 3. Server Field Requirement: I found that removing the server field from the linked repository configuration causes the pull repository task to run indefinitely without completing. ### Questions 1. Is it by design that linked repositories cannot trigger webhook deployments on stacks located on different servers? 2. If it is supported, how should webhooks be configured to properly trigger deployments across different servers? 3. Is there a specific network configuration required for cross-server webhook propagation? 4. Does using a linked repository require additional configuration to enable webhook-based deployments? ### Environment Komodo version: 1.19.4 OS: Linux Git provider: Self-hosted Git server Forgejo Deployment method: Docker I appreciate any insights on whether this is expected behavior or if I'm missing something in my configuration. Thank you!