Rework the e2e test to expect a working connection to a cluster when
they start. Developers can create their own clusters and run the tests.
Removed the code used to start kind clusters within the e2e tests.
Reworked the Taskfile to define two environments where the tests can run:
1. An ephemeral one running within Dagger, using the k3s module, to be
used by the CI.
2. A persistent one created with Kind, requiring the kind binary, to be
used for development and debugging when the ephemeral cluster is not
enough.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Signed-off-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com>
Co-authored-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com>
Run basic backup and restore tests for the plugin. Use MinIO for S3,
Azurite for ACS and fake-gcs-server for GCS.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Switch from using exec.Command to using kind and docker as libraries, so
tests won't depend on external binaries.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Create the CI and testing infrastructure for e2e testing. Running the ci
task now will push the plugin and sidecar images to a local registry,
start kind, install the CloudNativePG and cert-manager operators, and
then install the plugin-barman-cloud one.
No actual test is implemented.
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
