-
Notifications
You must be signed in to change notification settings - Fork 16
feat: support api key authentication and automatic query alias creation #1418
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
# [3.17.0-beta.2](v3.17.0-beta.1...v3.17.0-beta.2) (2026-02-11) ### Features * support api key authentication and automatic query alias creation ([#1418](#1418)) ([6e8e9f6](6e8e9f6))
|
🎉 This PR is included in version 3.17.0-beta.2 🎉 The release is available on:
Your semantic-release bot 📦🚀 |







Implements LIBS-802 and LIBS-400
Key features
apiTokenparameter to the data engine configChecklist
Known issues
useConfig. This is likely OK as it is most often going to be used in non-React contexts (server scripts) and if a malicious developer really wanted to snoop on this token they could even if we didn't pass it through in Context. However, we could decide to obfuscate / hide this parameter from downstream consumers and only use it for the data service...