chore(docs): explain how flux webhooks are set during maintenance #128

Closed

Ghostinvisible-forgejo-org wants to merge 0 commits from refs/pull/115/head4140aa2a7677eaf2c4dcdc011e55afe179480b36 into mainb7623d4bc2060d7314b1fa148acb2e859c9894df

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:26 +00:00

First-time contributor

Fixes infrastructure/k8s-cluster#112

Ghostinvisible-forgejo-org closed this pull request

2025-12-08 12:54:26 +00:00

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:27 +00:00

Author

First-time contributor

https://codeberg.org/forgejo/k8s-cluster/settings/hooks/9500 is activated
https://code.forgejo.org/infrastructure/k8s-cluster/settings/hooks/12 is deactivated

* https://codeberg.org/forgejo/k8s-cluster/settings/hooks/9500 is activated * https://code.forgejo.org/infrastructure/k8s-cluster/settings/hooks/12 is deactivated

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:27 +00:00

Author

First-time contributor

https://code.forgejo.org/infrastructure/k8s-cluster/pulls/113 was merged and the reconciliation happened, the webhooks works.

https://code.forgejo.org/infrastructure/k8s-cluster/pulls/113 was merged and the reconciliation happened, the webhooks works. ![image](/attachments/810b717a-1bcb-4871-99ad-fd46e7606b6a)

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:27 +00:00

Author

First-time contributor

i think it's ok to have both active because it will use only the configured repo to pull changes on trigger

I was thinking that, although it would not cause a persistent error, it would cause a flip flop during short time that may be mistaken for an error.

> i think it's ok to have both active because it will use only the configured repo to pull changes on trigger I was thinking that, although it would not cause a persistent error, it would cause a flip flop during short time that may be mistaken for an error.

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:27 +00:00

Author

First-time contributor

i think it's ok to have both active because it will use only the configured repo to pull changes on trigger

I was thinking that, although it would not cause a persistent error, it would cause a flip flop during short time that may be mistaken for an error.

what should flip flop? 🤔 flux will ignore the wrong hook

> > i think it's ok to have both active because it will use only the configured repo to pull changes on trigger > > I was thinking that, although it would not cause a persistent error, it would cause a flip flop during short time that may be mistaken for an error. what should flip flop? 🤔 flux will ignore the wrong hook

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:28 +00:00

Author

First-time contributor

Since the webhook is the same URL on both repositories, how can it know it is wrong?

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:28 +00:00

Author

First-time contributor

Since the webhook is the same URL on both repositories, how can it know it is wrong?

it checks the payload. maybe it just pulls the associated GitHub repo.

> Since the webhook is the same URL on both repositories, how can it know it is wrong? it checks the payload. maybe it just pulls the associated GitHub repo.

Ghostinvisible-forgejo-org commented

2025-12-08 12:54:28 +00:00

Author

First-time contributor

I think that's what it does because the flip flop happened when the GitRepository was changed to be codeberg.org, in the delay it took for the mirror to be updated. But I'm not sure. In any case, I think best to be strict and explicit so that kind of subtle behavior is not a concern.