github.com/argoproj/argo-events@v1.9.1/docs/eventsources/multiple-events.md (about)

     1  # EventSource With Multiple Events
     2  
     3  ![GA](../assets/ga.svg)
     4  
     5  > v0.17.0 and after
     6  
     7  Multiple events can be configured in a single EventSource, they can be either
     8  one event source type, or mixed event source types with some limitations.
     9  
    10  ## Single EventSource Type
    11  
    12  A single type EventSource configuration:
    13  
    14  ```yaml
    15  apiVersion: argoproj.io/v1alpha1
    16  kind: EventSource
    17  metadata:
    18    name: webhook
    19  spec:
    20    webhook:
    21      example:
    22        port: "12000"
    23        endpoint: /example
    24        method: POST
    25      example-foo:
    26        port: "13000"
    27        endpoint: /example2
    28        method: POST
    29  ```
    30  
    31  For the example above, there are 2 events configured in the EventSource named
    32  `webhook`.
    33  
    34  ## Mixed EventSource Types
    35  
    36  EventSource is allowed to have mixed types of events configured.
    37  
    38  ```yaml
    39  apiVersion: argoproj.io/v1alpha1
    40  kind: EventSource
    41  metadata:
    42    name: mixed-sources
    43  spec:
    44    webhook:
    45      webhook-example: # eventName
    46        port: "12000"
    47        endpoint: /example
    48        method: POST
    49    sns:
    50      sns-example: # eventName
    51        topicArn: arn:aws:sns:us-east-1:XXXXXXXX:test
    52        webhook:
    53          endpoint: "/"
    54          port: "15000"
    55        accessKey:
    56          key: my-key
    57          name: my-name
    58        secretKey:
    59          key: my-secret-key
    60          name: my-secret-name
    61        region: us-east-1
    62  ```
    63  
    64  However, there are some rules need to follow to do it:
    65  
    66  - EventSource types with `Active-Active` HA strategy can not be mixed with types
    67    with `Active-Passive` strategy, for EventSource types, see
    68    [EventSource High Availability](ha.md) for the detail.
    69  
    70  - Event Name (i.e. `webhook-example` and `sns-example` above, refer to
    71    [EventSource Names](naming.md)) needs to be unique in the EventSource, same
    72    `eventName` is not allowed even they are in different event source types.
    73  
    74    The reason for that is, we use `eventSourceName` and `eventName` as the
    75    dependency attributes in Sensor.