You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Until now the webhook key could only be generated by the server, which
does not play well with configuration as code: every time the resource
is re-applied the key changes and the repository webhook has to be
updated by hand.
The webhook_key field is now also writable (write only) on projects,
job templates and workflow job templates. When a key is supplied it is
kept as is, so the same secret can be stored in a vault and applied to
both the repository and the resource by automation. When the field is
left blank the previous behavior remains: a new key is generated
whenever the webhook service is set or changed, and blanking the key of
an active webhook generates a fresh one. Keys are never returned on the
resource itself, reading them still requires the webhook_key endpoint,
and copies of a resource always get their own key.
The key field in the UI is now an editable input with the same
semantics.
0 commit comments