feat(ee): add Pipeline.get_streams for NATS stream names (ETL-1188)#71
Merged
PabloPardoGarcia merged 1 commit intoJun 16, 2026
Conversation
Add ee.Pipeline.get_streams(), wrapping GET /api/v1/pipeline/{id}/streams. It
returns the pipeline's NATS JetStream streams as [{stream_name, component}],
useful for diagnosing NATS-level issues. 404 maps to PipelineNotFoundError and
403 to FeatureNotLicensedError. Enterprise-only, so it lives on ee.Pipeline.
Verified live against staging pipelines.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
PabloPardoGarcia
deleted the
pablo/etl-1188-sdk-add-method-to-get-pipeline-stream-names
branch
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
1 participant
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.
What
Implements ETL-1188: a method to fetch a pipeline's NATS JetStream stream names.
Stacked on #68 (ETL-1186) — base is
pablo/etl-1186-add-ee-client-to-sdk. Enterprise-only, so it lives onee.Pipeline.Details
ee.Pipeline.get_streams()wrapsGET /api/v1/pipeline/{id}/streamsand returns the streams as[{"stream_name": ..., "component": ...}](component is the data-plane stage the stream belongs to:ingestor/join/sink/dedup/dlq). Useful for diagnosing NATS-level issues (unblocks ETL-1101, NATS MCP diagnostics).404→PipelineNotFoundError;403→FeatureNotLicensedError.Testing
259 passed, ruff clean. Unit tests cover success, 204/empty, 404, and the 403 mapping.Verified live against staging:
client.get_pipeline(...).get_streams()returns the streams forotlp-logs-staging/otlp-metrics-staging, and a missing pipeline raisesPipelineNotFoundError.🤖 Generated with Claude Code