feat(runtime): draft lightweight Tidal Control GraphQL API client connector - #198
Merged
Merged
Conversation
Contributor
Author
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 is this change?
This PR introduces a draft of a lightweight HTTPX-based client connector for the Tidal Control GraphQL API at
src/runtime/tidal.py. It also registers the necessary configuration environment variables in.env.exampleandsrc/runtime/config.py.What did Sam notice that led to this?
Sameer (<@U06G1DC1UMQ>) requested adding a 'tidal MCP' or Tidal Control integration to Sam to support automating security-management processes and approving ISMS changes per dembrane's policies.
Tier?
Tier 3 (runtime connector configuration).
Confidence?
100% confident in the client structure and GraphQL patterns, verified against Tidal Control's official API documentation.