feat: Proof of concept for SQL --> timescale consumer queries #696
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
This is a proof of concept, skunkworks project to show how we might offer a high level, enterprise offering with direct access to our timescale / time series data off GitHub
cc @bdougie
Note: there is alot of work to do real validation of queries. This would currently be open to all kinds of sql injection attacks.
What type of PR is this? (check all applicable)
Related Tickets & Documents
N/a
Mobile & Desktop Screenshots/Recordings
Given a query in the API like:
This returns a list of data from the api like:
Steps to QA
Tier (staff will fill in)
[optional] Are there any post-deployment tasks we need to perform?
This is only a proof of concept. But gets the idea across. We'd want to guard this from public access while we iterate on it or drop it as one big feature.
[optional] What gif best describes this PR or how it makes you feel?