Forge Container services is now in Preview, and therefore fully supported. However, it remains under active development and may be subject to shorter deprecation windows. Preview features are suitable for early adopters in production environments.

We release preview features so partners and developers can study, test, and integrate them prior to General Availability (GA). For more details, see Forge EAP, Preview, and GA.

You can configure events to invoke your app’s container service. To enable this, first define the container service endpoint, following define endpoints. Use the event module’s endpoint property to specify which container service API to invoke. This endpoint property must match the key of a container service’s endpoint module.

All events are sent through an HTTP POST method.

Examples

Refer to the following manifest event snippets for examples:

Product trigger

Scheduled trigger

Async event trigger

Product trigger example

1
2
modules:
  trigger:
    - key: container-product-trigger-event
      endpoint: event-trigger-ep
      events:
        - avi:jira:commented:issue
  endpoint:
    - key: event-trigger-ep
      service: java-service
      route:
        path: /event-trigger
services:
  - key: java-service
    containers:
      - key: java-service
        tag: 1.0.0
        resources:
          cpu: "1"
          memory: "2Gi"
        health:
          type: http
          route:
            path: /health

For an implementation example, refer to this section of the sample app.