github-runner-webhook-router

GitHub Runner Webhook Router

  • Canonical IS DevOps
Channel Revision Published Runs on
latest/edge 43 Today
Ubuntu 22.04
juju deploy github-runner-webhook-router --channel edge
Show information

Platform:

Learn about actions >

  • redeliver-failed-webhooks

    Redeliver failed webhook deliveries since a certain time period. This action fetches the Github api for failed deliveries and triggers redelivery. Note that the amount of webhook deliveries that will be redelivered can be quite large and the requests are counted against the rate limit of the Github API. The action returns the amount of webhooks that were redelivered. Note that this action requires juju user secrets, which have been available since juju 3.3.

    Params
    • github-app-client-id string

      The client ID of the GitHub App to use for communication with GitHub, If provided, the other github-app-* params must also be provided. The Github App needs to have write permission for Webhooks. Either this or the github-token must be provided.

    • github-app-installation-id integer

      The app installation id of the GitHub App to use for communication with GitHub. If provided, the other github-app-* params must also be provided. The Github App needs to have write permission for Webhooks. Either this or the github-token must be provided.

    • github-app-private-key-secret-id string

      The juju user secret id of the private key to use for communication with GitHub. The key has to be provided in a field named 'private-key' in the secret. If provided, the other github-app-* params must also be provided. The Github App needs to have write permission for Webhooks. Either this or the github-token must be provided.

    • github-path string

      The path of the organisation or repository where the webhooks are registered. Should be in the format of <organisation> or <organisation>/<repository>.

    • github-token-secret-id string

      The juju user secret id of the token to use for communication with GitHub.The token has to be provided in a field named 'token' in the secret. This can be a PAT with write admin:repo_hook or a fine-grained token with write permission for Webhooks. Either this or the GitHub App configuration must be provided.

    • since integer

      The amount of seconds to look back for failed deliveries.

    • webhook-id integer

      The id of the webhook to redeliver.

    Required

    since, github-path, webhook-id

  • rotate-secret-key

    Rotate the secret key. Users will be forced to log in again. This might be useful if a security breach occurs.