Handling auth for 3rd-party services #13

New issue

Closed

opened 2026-07-27 16:41:57 +00:00 by erik · 1 comment

erik commented

2026-07-27 16:41:57 +00:00

Owner

Plugins such as the opensearch sink have no way to authenticate to its destination. The typescript port allowed endpoint to be a pipeline-defined function so that the env vars could be interpolated into the endpoint. Think of some good options. As a stop-gap solution, we could simply have plugins honor env vars (eg LOGBUS_OPENSEARCH_USERNAME), but that has at least these drawbacks:

no support for multiple opensearch instances (eg one for reading & one for writing)
some orgs do not like/allow env vars for auth

Plugins such as the opensearch sink have no way to authenticate to its destination. The typescript port allowed `endpoint` to be a pipeline-defined function so that the env vars could be interpolated into the endpoint. Think of some good options. As a stop-gap solution, we could simply have plugins honor env vars (eg LOGBUS_OPENSEARCH_USERNAME), but that has at least these drawbacks: - no support for multiple opensearch instances (eg one for reading & one for writing) - some orgs do not like/allow env vars for auth

erik self-assigned this

2026-07-27 16:41:57 +00:00

erik commented

2026-08-14 17:46:00 +00:00

Author

Owner

#15 should address this sufficiently well for now.

erik closed this issue

2026-08-14 17:46:00 +00:00