Add ability to define what kind of keys are stored prod/staging #347
Conversation
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
Release version 4.13.0
This was referenced Jan 11, 2024
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
This PR adds ability to define what kind of keys are stored
prod/staging:prod/stagingis detected by existing thestagingstring in therestUrlconfig option:https://api-pub.bitfinex.com/https://api.staging.bitfinex.comisStagingBfxApiflag is set or updated on signUp/signIn to theusertablegetUsersendpoint will return theisStagingBfxApiflag to be shown in the UI for each user on the login stageBasic changes:
isStagingBfxApiendpointisStagingBfxApiflag forsignInendpointisStagingBfxApiflag forgetUsersendpointisStagingBfxApiflag onsign-up/sign-inv39DB migrationisStagingBfxApiisStagingBfxApirequest example:{ "method": "isStagingBfxApi" }isStagingBfxApiresponse example:{ "jsonrpc": "2.0", "result": false, "id": null }signInrequest example:{ "auth": { "email": "user@email.com", "isSubAccount": false }, "method": "signIn" }signInresponse example:{ "jsonrpc": "2.0", "result": { "email": "user@email.com", "isSubAccount": false, "token": "559cb736-ffdd-4f7d-9a53-362d913bdc16", "shouldNotSyncOnStartupAfterUpdate": false, "authTokenTTLSec": null, "localUsername": null, "lastSyncMts": 1704177514708, "isStagingBfxApi": false // The flag }, "id": null }getUsersrequest example:{ "method": "getUsers" }getUsersresponse example:{ "jsonrpc": "2.0", "result": [ { "email": "user@email.com", "localUsername": null, "isSubAccount": false, "isNotProtected": true, "subUsers": [], "isRestrictedToBeAddedToSubAccount": true, "isApiKeysAuth": false, "isStagingBfxApi": false // The flag }, { "email": "user+1@email.com", "localUsername": null, "isSubAccount": false, "isNotProtected": true, "subUsers": [], "isRestrictedToBeAddedToSubAccount": false, "isApiKeysAuth": true, "isStagingBfxApi": true // The flag } ], "id": null }