This PR addresses the issue raised here (and originally in #224) by adding a new "Auth Token" setting to the "Extra Settings" tab in the server connection modal. The inputted value will then be sent as the X-Dgraph-AuthToken HTTP header on requests to the server.
I'm not familar with the Ratel codebase, so it's possible that I've missed something! I've followed the same pattern used for the Slash API Key for consistency.
When I ran ./scripts/build.prod.sh it made updates to yarn.lock and package-lock.json, however I presumed these changes should not be commited as this PR does not introduce any new depedencies.
This PR addresses the issue raised here (and originally in #224) by adding a new "Auth Token" setting to the "Extra Settings" tab in the server connection modal. The inputted value will then be sent as the
X-Dgraph-AuthToken
HTTP header on requests to the server.I'm not familar with the Ratel codebase, so it's possible that I've missed something! I've followed the same pattern used for the Slash API Key for consistency.
When I ran
./scripts/build.prod.sh
it made updates toyarn.lock
andpackage-lock.json
, however I presumed these changes should not be commited as this PR does not introduce any new depedencies.This change is
Ratel Preview: