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
* storage can access the user's datcore tokens info
- storage service retrieves user token's key and secret when it needs to operate on external services
- finishes implementation calls to list datcore from wrapper
- fixes on front-end (@odeimaiz )
* closes#369
* merged squashed is309/storage-api-spec from PR #366 (pending review but tests passing)
* Removed session from storage. not needed.
* Cleanup storage submodule in web-server
- adds body in request
* Injected datcore tokens into dsm
* renamed: db_helpers.py -> db_tokens.py
* Fixed dev-config in storage (does not have entire root folder inside of the container!)
Added acces stdin_open and tty to attach for debuggin
* Fixes pytest warning
"cannot collect test class 'TestClient' because it has a __init__ constructor"
Pytest tries to collect TestClient as its name matches the naming conventions for test classes. However it finds a __init__ method, which it cannot understand.
* Modified storage config schemas on datcore test tokens
* Does not update dsm.datcore_tokens if not not available
* Fixes case of empty token match
* Injects dummy tokens table to init postgres fixture
userid is an integer but not a string
removed deprecated @pytest.mark.asyncio
the cleanest and fastest solution is to send the tokens on every call from webserver->storage ... the same way we do with the userid!
These can also go as part of the headers (get operations have them as well) or in some cookies... so they get bounced back and forward?
Child of #240
The text was updated successfully, but these errors were encountered: