You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add a parameter to the sql api so a project could specify a token and not be limited by the query limits of the api. The use case is our own internal applications that would prefer to use the json api for queries. This should be allowed for a restricted set of accounts.
Internal Use
Acceptance Criteria
Definition of Done
Tested against acceptance criteria
Tested against the assumptions of the user story
The project builds without errors
Unit tests are written and passing
Tests on devices/browsers listed in the issue have passed
QA performed & issues resolved
Refactoring completed
Any configuration or build changes documented
Documentation updated
Peer Code Review performed
The text was updated successfully, but these errors were encountered:
filipnyquist
added a commit
to LBRYFoundation/lbry-wunderbot
that referenced
this issue
Oct 24, 2018
This is now unblocked by 5b6a4c1. We now have authorization api keys. The solution now is to setup a new read only API account that is unlimited for our internal services. Depending on if a key is provided different read only mysql accounts are used.
Add a parameter to the sql api so a project could specify a token and not be limited by the query limits of the api. The use case is our own internal applications that would prefer to use the json api for queries. This should be allowed for a restricted set of accounts.
Internal Use
Acceptance Criteria
Definition of Done
The text was updated successfully, but these errors were encountered: