Skip to content

Commit

Permalink
cli open api update > fix openapi.yaml
Browse files Browse the repository at this point in the history
  • Loading branch information
DC2-DanielKrueger committed Jul 14, 2023
1 parent c3686bb commit df36c66
Showing 1 changed file with 10 additions and 10 deletions.
20 changes: 10 additions & 10 deletions specs/hivemq-openapi.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -135,16 +135,16 @@ tags:
### Restore Requirements
The requirements to successfully restore data from a backup are:
- A clean HiveMQ deployment. This means that no clients must be connected and no persistent data exists on every HiveMQ node. The import will not start if there is data available in your cluster.
- Message data used by Extensions are only restored if the corresponding extension is already started before the restore is started.
name: Backup & Restore
- description: |-
This endpoint can be used to create diagnostic archives.
More information about the diagnostic archive can be found in the [HiveMQ documentation](https://www.hivemq.com/docs/hivemq/latest/control-center/diagnostic-archive.html).
### Diagnostic Archive Requirements
- A clean HiveMQ deployment. This means that no clients must be connected and no persistent data exists on every HiveMQ node. The import will not start if there is data available in your cluster.
- Message data used by Extensions are only restored if the corresponding extension is already started before the restore is started.
name: Backup & Restore
- description: |-
This endpoint can be used to create diagnostic archives.
More information about the diagnostic archive can be found in the [HiveMQ documentation](https://www.hivemq.com/docs/hivemq/latest/control-center/diagnostic-archive.html).
### Diagnostic Archive Requirements
Some prerequisites are necessary to create a diagnostic archive:
- Only HiveMQ nodes with at least version 4.11.0 will create an archive
Expand Down

0 comments on commit df36c66

Please sign in to comment.