## pyre admin hubs accept-deletions

Let a replica's next data pass mirror a primary that shrank (one pass)

### Synopsis

A replica refuses a data pass that would delete more than a quarter of
what it holds -- a wiped primary must not be mirrored within minutes.
When the primary really did shrink (a purge, big volumes deleted, an
account reset) every pass since is refused and "replication" shows the
pass FAILED with the delete guard's count. This accepts it for ONE pass:
the replica mirrors the primary's deletions now, and the guard is back
for the pass after. Nothing is deleted on the primary.

```
pyre admin hubs accept-deletions <hub> [flags]
```

### Examples

```
  pyre admin hubs accept-deletions hub-a --yes
```

### Options

```
  -h, --help   help for accept-deletions
```

### Options inherited from parent commands

```
      --api string       API base URL (default from the profile, or https://api.pyredata.io)
      --ca-cert string   PEM file with an extra CA to trust (self-hosted managers)
      --insecure         skip TLS certificate verification (lab use only)
  -o, --output string    output format: table, json or plain (default "table")
      --profile string   config profile to use (see: pyre config)
  -q, --quiet            print results only, no notices
      --token string     API token (default from the profile; prefer PYRE_TOKEN in scripts)
  -y, --yes              answer yes to every confirmation (for scripts)
```

### SEE ALSO

* [pyre admin hubs](pyre_admin_hubs.md)	 - Add, build, promote, demote and remove hubs