WebhookDefinition
¶
Used by
-
AsyncCodePipelineClient Operationsput_webhook -
CodePipelineClient Operationsput_webhook
Source code in docs_src/capo_codepipeline/types/webhook_definition.py
authentication
instance-attribute
¶
authentication: WebhookAuthenticationType
Supported options are GITHUB_HMAC, IP, and UNAUTHENTICATED.
When creating CodePipeline webhooks, do not use your own credentials or reuse the same secret token across multiple webhooks. For optimal security, generate a unique secret token for each webhook you create. The secret token is an arbitrary string that you provide, which GitHub uses to compute and sign the webhook payloads sent to CodePipeline, for protecting the integrity and authenticity of the webhook payloads. Using your own credentials or reusing the same token across multiple webhooks can lead to security vulnerabilities.
If a secret token was provided, it will be redacted in the response.
-
For information about the authentication scheme implemented by GITHUB_HMAC, see Securing your webhooks on the GitHub Developer website.
-
IP rejects webhooks trigger requests unless they originate from an IP address in the IP range whitelisted in the authentication configuration.
-
UNAUTHENTICATED accepts all webhook trigger requests regardless of origin.
authentication_configuration
instance-attribute
¶
authentication_configuration: WebhookAuthConfiguration
Properties that configure the authentication applied to incoming webhook trigger requests. The required properties depend on the authentication type. For GITHUB_HMAC, only the SecretToken property must be set. For IP, only the AllowedIPRange property must be set to a valid CIDR range. For UNAUTHENTICATED, no properties can be set.
filters
instance-attribute
¶
filters: WebhookFilters
A list of rules applied to the body/payload sent in the POST request to a webhook URL. All defined rules must pass for the request to be accepted and the pipeline started.
target_action
instance-attribute
¶
target_action: ActionName
The name of the action in a pipeline you want to connect to the webhook. The action must be from the source (first) stage of the pipeline.
target_pipeline
instance-attribute
¶
target_pipeline: PipelineName
The name of the pipeline you want to connect to the webhook.