Nessie 0.94.2
- 8 commits since 0.94.1
- Maven Central: https://search.maven.org/search?q=g:org.projectnessie.nessie+v:0.94.2
- Docker images: https://github.com/projectnessie/nessie/pkgs/container/nessie and https://quay.io/repository/projectnessie/nessie?tab=tags
It is a multiplatform Java image (amd64, arm64, ppc64le, s390x):docker pull ghcr.io/projectnessie/nessie:0.94.2-java - PyPI: https://pypi.org/project/pynessie/ (See pynessie)
- Helm Chart repo: https://charts.projectnessie.org/
Try it
The attached nessie-quarkus-0.94.2-runner.jar is a standalone uber-jar file that runs on Java 17 or newer and it is also available via Maven Central. Download and run it (requires Java 17):
wget https://github.com/projectnessie/nessie/releases/download/nessie-0.94.2/nessie-quarkus-0.94.2-runner.jar
java -jar nessie-quarkus-0.94.2-runner.jar
Nessie CLI is attached as nessie-cli-0.94.2.jar, which is a standalone uber-jar file that runs on Java 11 or newer. Nessie CLI is also available as a Docker image: docker run --rm -it ghcr.io/projectnessie/nessie-cli:0.94.2.
Nessie GC tool is attached as nessie-gc-0.94.2.jar, which is a standalone uber-jar file that runs on Java 11 or newer. Shell completion can be generated from the tool, check its help command. Nessie GC tool is also available as a Docker image: docker run --rm ghcr.io/projectnessie/nessie-gc:0.94.2 --help.
Nessie Server Admin tool is attached as nessie-server-admin-tool-0.94.2-runner.jar, which is a standalone uber-jar file that runs on Java 17 or newer. Shell completion can be generated from the tool, check its help command. Nessie Server Admin tool is also available as a Docker image: docker run --rm ghcr.io/projectnessie/nessie-server-admin:0.94.2 --help.
The attached nessie-helm-0.94.2.tgz is a packaged Helm chart, which can be downloaded and installed via Helm. There is also the Nessie Helm chart repo, which can be added and used to install the Nessie Helm chart.
Changelog
Highlights
-
Helm chart: it is now possible to use Helm templating in all values; any built-in
object can be specified. This is
particularly useful for dynamically passing the namespace to the Helm chart, but cross-referencing
values from different sections is also possible, e.g.:mongodb: name: nessie connectionString: mongodb+srv://mongodb.{{ .Release.Namespace }}.svc.cluster.local:27017/{{ .Values.mongodb.name }}
The above would result in the following properties when deploying to namespace
nessie-ns:quarkus.mongodb.database=nessie quarkus.mongodb.connection-string=mongodb://mongodb.nessie-ns.svc.cluster.local:27017/nessie