Repository navigation
Conversation
etserend
changed the title
…(SAO-18181) O11y CRUD requests now target https://api.{realm}.observability.splunkcloud.com instead of https://app.{realm}.observability.splunkcloud.com. Add optional SPLUNK_AO_O11Y_API_URL to override the CRUD API origin: https only, origin only (no path, credentials, query or fragment), with the origin rebuilt from host and port. The override counts as O11y configuration and is reported by the auth guard when the realm is missing. The OTLP ingest endpoint and the console URL are unchanged. Co-Authored-By: Claude <noreply@anthropic.com>
etserend
force-pushed
the
fix/sao-18181-o11y-api-host
branch
from
November 3, 2026 01:15
a72e9b4 to
8223cdc
Compare
etserend
marked this pull request as ready for review
November 3, 2026 01:18
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The SDK hardcoded
app.{realm}.observability.splunkcloud.comfor O11y CRUD requests with no way to override the endpoint. This change moves the default CRUD host and adds an optional override. Jira: SAO-18181.https://api.{realm}.observability.splunkcloud.com(wasapp.).SPLUNK_AO_O11Y_API_URLoverrides the CRUD API origin only. It must be anhttps://origin with no path, credentials, query or fragment. It counts as O11y configuration, so it conflicts with the standalone variables. Errors never echo the value.app.{realm}).Testing
tests/test_deployment.py,tests/test_o11y_config.py): 128 passed (addstests/test_config.py), including new override, validation and auth-guard tests.main. The pre-existing failures also occur onmainwithout this change (OTLP exporter import, OpenAI, serialization).Projects().list()) through the test pipeline lab0 -> rc0 -> us1 (us1 is production). Each realm succeeds on the new default host and through an explicit override:GETapp./api.api.{realm}.observability.splunkcloud.comhttps://api.{realm}.signalfx.comOpen items before merge
SPLUNK_AO_O11Y_API_URLname (public surface).Not covered: an override for the OTLP ingest endpoint, and custom CA/TLS configuration.