Currently, users must manually provide organization and Dispatch API endpoint when creating an event driver. This change removes this burden from the user by adding an option to configure api-endpoint accessible by event drivers, as well as it adds authentication for event drivers by requiring them to specify a token. The token is used to retrieve the organization server-side.
Changes
Add configuration option and flag (api-endpoint) to specify API endpoint to which Docker-based event drivers must send events
Use event driver ID as an authentication token for ingesting events
Add new endpoint /ingest for ingesting events from event drivers, using above auth token (dropping the requirement of providing org ID in the header)
Inject api endpoint and auth token into event drivers at deployment time
Overview
Currently, users must manually provide organization and Dispatch API endpoint when creating an event driver. This change removes this burden from the user by adding an option to configure api-endpoint accessible by event drivers, as well as it adds authentication for event drivers by requiring them to specify a token. The token is used to retrieve the organization server-side.
Changes
api-endpoint) to specify API endpoint to which Docker-based event drivers must send events/ingestfor ingesting events from event drivers, using above auth token (dropping the requirement of providing org ID in the header)Testing
e2e with enabled events passed.
Fix #699 Fix #700