To reduce the security alerts we update the dagger modules: check-doc-version
and gotest to the latest versions inside the go.mod files
Closes#300
Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
The latest version v0.1.10 fix the issue #297 that was producing that
the CI failed every time because of the cache didn't exists and needed
to wait for the server to start.
Closes#297
Signed-off-by: Jonathan Gonzalez V. <jonathan.gonzalez@enterprisedb.com>
Rework the documentation to be a static website instead of just the
GitHub README.md. Use docusaurus to create the website, and the CI to
publish to GitHub pages on commits to main.
Block `release-please` releases unless the documentation for that version
has been generated.
Closes#244
Signed-off-by: Francesco Canovai <francesco.canovai@enterprisedb.com>
Signed-off-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
Co-authored-by: Leonardo Cecchi <leonardo.cecchi@enterprisedb.com>
Co-authored-by: Gabriele Bartolini <gabriele.bartolini@enterprisedb.com>
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>
