Skip to content
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

remove reference to /admin/{backup,export} endpoints #586

Merged
merged 1 commit into from
Aug 3, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions content/deploy/admin/dgraph-administration.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,10 +24,8 @@ Admin endpoints usually start with the `/admin` path. The current list of admin
endpoints includes the following:

* `/admin`
* `/admin/backup`
* `/admin/config/cache_mb`
* `/admin/draining`
* `/admin/export`
* `/admin/shutdown`
* `/admin/schema`
* `/admin/schema/validate`
Expand Down
2 changes: 1 addition & 1 deletion content/deploy/cli-command-reference.md
Original file line number Diff line number Diff line change
Expand Up @@ -637,7 +637,7 @@ help listing shown when you run `dgraph restore --help`:
```shell
Restore loads objects created with the backup feature in Dgraph Enterprise Edition (EE).

Backups are originated from HTTP at /admin/backup, then can be restored using CLI restore
Backups taken using the GraphQL API can be restored using CLI restore
command. Restore is intended to be used with new Dgraph clusters in offline state.

The --location flag indicates a source URI with Dgraph backup objects. This URI supports all
Expand Down
2 changes: 0 additions & 2 deletions content/deploy/dgraph-alpha.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,8 +10,6 @@ Dgraph Alpha provides several HTTP endpoints for administrators, as follows:

* `/health?all` returns information about the health of all the servers in the cluster.
* `/admin/shutdown` initiates a proper [shutdown]({{< relref "dgraph-administration.md#shutting-down-database" >}}) of the Alpha.
* `/admin/export` initiates a data [export]({{< relref "dgraph-administration.md#exporting-database" >}}). The exported data will be
encrypted if the alpha instance was configured with an encryption key file.

By default the Alpha listens on `localhost` for admin actions (the loopback address only accessible from the same machine). The `--bindall=true` option binds to `0.0.0.0` and thus allows external connections.

Expand Down
7 changes: 4 additions & 3 deletions content/deploy/security/tls-configuration.md
Original file line number Diff line number Diff line change
Expand Up @@ -349,16 +349,17 @@ succeed.

## Using Curl with Client authentication

When TLS is enabled, `curl` requests to Dgraph will need some specific options to work. For instance (for an export request):
When TLS is enabled, `curl` requests to Dgraph will need some specific options to work.
For instance (for changing draining mode):

```
curl --silent https://localhost:8080/admin/export
curl --silent https://localhost:8080/admin/draining
```

If you are using `curl` with [Client Authentication](#client-authentication-options) set to `REQUIREANY` or `REQUIREANDVERIFY`, you will need to provide the client certificate and private key. For instance (for an export request):

```
curl --silent --cacert ./tls/ca.crt --cert ./tls/client.dgraphuser.crt --key ./tls/client.dgraphuser.key https://localhost:8080/admin/export
curl --silent --cacert ./tls/ca.crt --cert ./tls/client.dgraphuser.crt --key ./tls/client.dgraphuser.key https://localhost:8080/admin/draining
```

Refer to the `curl` documentation for further information on its TLS options.
Expand Down