Synchronous HTTP transport
HttpTransport.RdSends OpenLineage events as JSON POST requests. The base url and
relative endpoint are joined with one slash; a URL that already ends in
the endpoint is not duplicated.
Supply api_key for Authorization: Bearer <key> authentication, or place
authentication headers in headers. Supplying both an API key and a custom
Authorization header is an error. All custom headers are redacted from
httr2 request printing.
HTTP 429, 500, 502, 503, and 504 responses and low-level connection
failures are retried up to max_retries times. HTTP 401 and 403 responses
are never retried. Set verify_tls = FALSE only for controlled development
environments; doing so raises an openlineage_insecure_tls_warning.
Methods
Inherited methods
OpenLineageTransport$close()
HttpTransport$new()
Create an HTTP transport.
Usage
HttpTransport$new(
url,
endpoint = "api/v1/lineage",
api_key = NULL,
headers = character(),
timeout = 5,
verify_tls = TRUE,
max_retries = 3L
)Arguments
urlAn absolute HTTP or HTTPS base URL.
endpointA relative OpenLineage endpoint path.
api_keyAn optional bearer API key.
headersOptional custom headers as a named character vector.
timeoutA positive request timeout in seconds.
verify_tlsWhether to verify TLS certificates.
max_retriesA non-negative number of retries after the first request attempt.