feat!: use tracking_api_key instead of the old api_key and secret #80
Conversation
This file contains 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
Yihao-G
force-pushed
the
feature/feat_use_tracking_api_key_instead_of_the_old_api_key_and_secret
branch
3 times, most recently
from
17a7b6b to
c26dcf5
Compare
jylamont
force-pushed
the
feature/feat_use_tracking_api_key_instead_of_the_old_api_key_and_secret
branch
from
c26dcf5 to
188001e
Compare
This was referenced Jan 7, 2025
jylamont
approved these changes
Feb 4, 2025
jylamont
deleted the
feature/feat_use_tracking_api_key_instead_of_the_old_api_key_and_secret
branch
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.
The new tracking API keys replace the existing API keys, secrets and auth tokens.
This PR updates the SDK to accept the tracking API keys, and removes the support for API keys and secrets.
BREAKING CHANGE: remove the support of
api_keyandsecretas a way of authentication.