Updated Tinybird config and instructions for using JWTs#18
Merged
Conversation
Contributor
Author
|
Pretty sure this is everything we need, just waiting on Tinybird to enable the JSON field on my workspace to test it out tomorrow. |
02a8203 to
215794e
Compare
9aa4b81 to
d78809c
Compare
d78809c to
018514d
Compare
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.
We've switched from using the static
stats_tokento generating dynamic JWTs for querying Tinybird's endpoints. The workspace ID and admin token are required to sign the JWTs, so we need to add those to the configuration. The stats token is no longer used, so this also removes it.It also adds the labs flag via config to allow enabling analytics in the
.envfile, instead of requiring the user to enable it in the UI.