Forge Containers are now available through Forge's Early Access Program (EAP). To start testing this feature, submit your app's ID to our team through this link.

EAPs are offered to selected users for testing and feedback purposes. APIs and features under EAP are unsupported and subject to change without notice. APIs and features under EAP are not recommended for use in production environments.

For more details, see Forge EAP, Preview, and GA.

To invoke a container service or make calls from one, you'll need to first define its endpoint. See Define endpoints for details.

You can configure events to invoke your app’s container service. To enable this, 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.