Description
Describe the bug
Following the recent rotation of the GitLab token used by our Argo-Events source (GitLab), we encountered an incident. After updating the secret value via external secrets, the logs indicated that the source appeared to function correctly.
...,"msg":"received a request, processing it...",...
Upon further investigation, it was discovered that the webhook configurations had not been updated with the new token automatically. This necessitated manual intervention, where all existing webhooks had to be deleted to allow the EventSource to recreate them with the updated token configuration.
To Reproduce
- Create gitlab event source
- Create some trigger to display the message
- Rotate the gitlab token updating in your argo-events app
- At this time the trigger is not more dispatching
Expected behavior
After rotate the gitlab token, reconfigure webhooks
Environment (please complete the following information):
- Kubernetes: v1.30.0
- Argo Events: 1.7.5
Message from the maintainers:
If you wish to see this enhancement implemented please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
Activity