Merged
Conversation
feat: add optional logger for orchestrator API requests
fix: thread logger through all getOrchestrator call sites
fix: pass logger in RhinestoneSDK.createAccount config
…xecution-ssx fix: target execution typedata
Allow users to pass a custom Authorization header to all SDK requests made to the orchestrator endpoint by specifying authorizationHeader in RhinestoneSDKConfig. This enables authorization flows beyond the existing x-api-key header. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
Add optional Authorization header to orchestrator requests
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
3 participants
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.
Description
Checklist