marco/plugin-barman-cloud
1
0
Fork 0
mirror of https://github.com/cloudnative-pg/plugin-barman-cloud.git synced 2026-07-06 17:52:21 +02:00
Code Issues Packages Projects Releases Wiki Activity
c5f149b86a
plugin-barman-cloud/web
History
Armando Ruocco c5f149b86a
Some checks failed
Deploy Docusaurus to GitHub Pages / build (push) Failing after 5s
Details
Deploy Docusaurus to GitHub Pages / deploy (push) Has been skipped
Details
release-please / release-please (push) Failing after 3s
Details
feat: pass additionalCommandArgs to barman-cloud-restore (#914) 
An `ObjectStore` already lets users tack extra command-line flags onto
three of the four `barman-cloud-*` invocations: `barman-cloud-backup`
via
`data.additionalCommandArgs`, `barman-cloud-wal-archive` via
`wal.archiveAdditionalCommandArgs`, and `barman-cloud-wal-restore` via
`wal.restoreAdditionalCommandArgs`. The fourth — `barman-cloud-restore`,
the actual data-restore step in PITR and recovery-from-object-store —
has had no
equivalent, which is exactly the gap reported in #821 (the asker wanted
a longer `--read-timeout` for slow restores from S3).

This PR fills that gap by adding
`spec.configuration.data.restoreAdditionalCommandArgs` and wiring it
into the recovery job hook. In `restoreDataDir`,
the user-supplied flags are appended after the cloud-provider options
and `--endpoint-url` but before the positional `(destinationPath,
serverName,
backupID, pgdata)` arguments — same shape as the other three knobs. The
library's existing append/dedup logic still wins on conflicts, so users
can't
accidentally override flags the plugin already sets (`--cloud-provider`,
`--endpoint-url`, etc.).

Closes #821

Signed-off-by: Armando Ruocco <armando.ruocco@enterprisedb.com>
Signed-off-by: Leonardo Cecchi <leonardo.cecchi@gmail.com>
Co-authored-by: Leonardo Cecchi <leonardo.cecchi@gmail.com>
2026-06-03 14:17:12 +02:00
..
docs feat: pass additionalCommandArgs to barman-cloud-restore (#914) 2026-06-03 14:17:12 +02:00
src docs: autoselect version (#344) 2025-05-15 13:36:57 +02:00
static docs: publish docs with docusaurus (#268) 2025-04-30 12:17:57 +02:00
versioned_docs fix(docs): update broken link to CloudNativePG documentation (#904) 2026-05-12 10:46:04 +02:00
versioned_sidebars docs(release): documentation for release 0.12.0 (#848) 2026-04-13 17:48:48 +02:00
.gitignore chore: use yarn lockfile instead of npm one (#314) 2025-05-06 12:08:25 +02:00
docusaurus.config.ts docs: publish docs with docusaurus (#268) 2025-04-30 12:17:57 +02:00
package.json fix(deps): update documentation dependencies to v3.10.1 (#878) 2026-05-06 08:26:23 +02:00
README.md docs: add backup, WAL archive and recovery information (#291) 2025-05-06 11:49:09 +02:00
sidebars.ts docs: publish docs with docusaurus (#268) 2025-04-30 12:17:57 +02:00
tsconfig.json docs: autoselect version (#344) 2025-05-15 13:36:57 +02:00
versions.json docs(release): documentation for release 0.12.0 (#848) 2026-04-13 17:48:48 +02:00
yarn.lock chore(deps): lock file maintenance (#922) 2026-05-25 10:52:58 +02:00

README.md

Website

This website is built using Docusaurus, a modern static website generator.

Requirements

Installation

$ yarn

Local Development

$ yarn start

This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.

Build

$ yarn build

This command generates static content into the build directory and can be served using any static contents hosting service.

Test the build

$ yarn serve

By default, this will load your site at http://localhost:3000/.

Spellchecking

From the top directory:

task spellcheck

Versioning

Docusaurus allows versioning of the documentation to maintain separate sets of documentation for different software versions.

To create a new documentation version:

$ yarn docusaurus docs:version X.Y.Z