github.com/argoproj/argo-events@v1.9.1/examples/event-sources/bitbucket.yaml (about)

     1  apiVersion: argoproj.io/v1alpha1
     2  kind: EventSource
     3  metadata:
     4    name: bitbucket
     5  spec:
     6    service:
     7      ports:
     8        - port: 12000
     9          targetPort: 12000
    10    bitbucket:
    11      # bitbucket eventsource example with basic auth strategy
    12      example:
    13        # Bitbucket repository list
    14        repositories:
    15          - owner: "name-of-owner" # owner of the repository
    16            repositorySlug: "name-of-repository1" # repository slug
    17          - owner: "name-of-owner"
    18            repositorySlug: "name-of-repository2"
    19        # events to listen to
    20        # Visit https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/
    21        events:
    22          - repo:push
    23        # Bitbucket will send webhook events to the following port and endpoint
    24        webhook:
    25          # endpoint to listen to events on
    26          endpoint: /push
    27          # port to run internal HTTP server on
    28          port: "12000"
    29          # HTTP request method to allow. In this case, only POST requests are accepted
    30          method: POST
    31          # url the event-source will use to register in Bitbucket.
    32          # This url must be reachable from outside the cluster.
    33          # The name for the service is in `<event-source-name>-eventsource-svc` format.
    34          # You will need to create an Ingress or Openshift Route for the event-source service so that it can be reached from Bitbucket.
    35          url: http://url-that-is-reachable-from-bitbucket
    36        # Delete the webhook when the eventsource is deleted
    37        deleteHookOnFinish: true
    38        auth:
    39  #        # oauthToken refers to K8s secret that stores the bitbucket OAuth bearer token
    40  #        # Visit https://support.atlassian.com/bitbucket-cloud/docs/use-oauth-on-bitbucket-cloud/
    41  #        oauthToken:
    42  #          # Name of the K8s secret that contains the oauth token
    43  #          name: bitbucket-access
    44  #          # Key within the K8s secret whose corresponding value (must be base64 encoded) is oauth token
    45  #          key: token
    46  
    47          # basic refers to Basic Auth strategy and can be used with App passwords
    48          # Visit https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/
    49          basic:
    50            # username refers to K8s secret that stores the bitbucket username
    51            username:
    52              # Name of the K8s secret that contains the username
    53              name: bitbucket-access
    54              # Key within the K8s secret whose corresponding value (must be base64 encoded) is username
    55              key: username
    56            # password refers to K8s secret that stores the bitbucket password (including App passwords)
    57            password:
    58              # Name of the K8s secret that contains the password
    59              name: bitbucket-access
    60              # Key within the K8s secret whose corresponding value (must be base64 encoded) is password
    61              key: password
    62  
    63  
    64  #    # bitbucket eventsource example with deprecated syntax using basic auth strategy
    65  #    example-with-deprecated-repo-syntax:
    66  #      # owner of the repository
    67  #      owner: "name-of-repo-owner"
    68  #      # repository slug
    69  #      repositorySlug: "name-of-repository"
    70  #      # Bitbucket will send events to following port and endpoint
    71  #      webhook:
    72  #        # endpoint to listen to events on
    73  #        endpoint: /push
    74  #        # port to run internal HTTP server on
    75  #        port: "12000"
    76  #        # HTTP request method to allow. In this case, only POST requests are accepted
    77  #        method: POST
    78  #        # url the event-source will use to register in Bitbucket.
    79  #        # This url must be reachable from outside the cluster.
    80  #        # The name for the service is in `<event-source-name>-eventsource-svc` format.
    81  #        # You will need to create an Ingress or Openshift Route for the event-source service so that it can be reached from Bitbucket.
    82  #        url: http://url-that-is-reachable-from-bitbucket
    83  #      # events to listen to
    84  #      # Visit https://support.atlassian.com/bitbucket-cloud/docs/manage-webhooks/
    85  #      events:
    86  #        - repo:push
    87  #      auth:
    88  #        # basic refers to Basic Auth strategy and can be used with App passwords
    89  #        # Visit https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/
    90  #        basic:
    91  #          # username refers to K8s secret that stores the bitbucket username
    92  #          username:
    93  #            # Name of the K8s secret that contains the username
    94  #            name: bitbucket-access
    95  #            # Key within the K8s secret whose corresponding value (must be base64 encoded) is username
    96  #            key: username
    97  #          # password refers to K8s secret that stores the bitbucket password (including App passwords)
    98  #          password:
    99  #            # Name of the K8s secret that contains the password
   100  #            name: bitbucket-access
   101  #            # Key within the K8s secret whose corresponding value (must be base64 encoded) is password
   102  #            key: password
   103  #      # Delete the webhook when the eventsource is deleted
   104  #      deleteHookOnFinish: true