Update Hexkit for all (#70)

* update monorepo dependencies * version bump all services
ghga-de · Nov 18, 2024 · 60ebd90 · 60ebd90
1 parent a53609d
commit 60ebd90
Show file tree

Hide file tree

Showing 24 changed files with 328 additions and 362 deletions.
diff --git a/.pre-commit-config.yaml b/.pre-commit-config.yaml
@@ -49,7 +49,7 @@ repos:
       - id: no-commit-to-branch
         args: [--branch, dev, --branch, int, --branch, main]
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.7.2
+    rev: v0.7.4
     hooks:
       - id: ruff
         args: [--fix, --exit-non-zero-on-fix]

diff --git a/.pyproject_generation/pyproject_custom.toml b/.pyproject_generation/pyproject_custom.toml
@@ -6,7 +6,7 @@ dependencies = [
     "typer >= 0.12",
     "ghga-service-commons[api, auth, crypt] >= 3.1",
     "ghga-event-schemas >= 3.3",
-    "hexkit[akafka, s3, mongodb] >= 3.6",
+    "hexkit[akafka, s3, mongodb] >= 3.7",
     "crypt4gh>=1.6",
     "hvac>=2",
     "httpx>=0.27",

diff --git a/lock/requirements-dev.txt b/lock/requirements-dev.txt
diff --git a/lock/requirements.txt b/lock/requirements.txt
diff --git a/pyproject.toml b/pyproject.toml
@@ -6,7 +6,7 @@ dependencies = [
     "typer >= 0.12",
     "ghga-service-commons[api, auth, crypt] >= 3.1",
     "ghga-event-schemas >= 3.3",
-    "hexkit[akafka, s3, mongodb] >= 3.6",
+    "hexkit[akafka, s3, mongodb] >= 3.7",
     "crypt4gh>=1.6",
     "hvac>=2",
     "httpx>=0.27",

diff --git a/services/dcs/README.md b/services/dcs/README.md
@@ -43,21 +43,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/download-controller-service):
 ```bash
-docker pull ghga/download-controller-service:2.0.4
+docker pull ghga/download-controller-service:2.0.5
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/download-controller-service:2.0.4 .
+docker build -t ghga/download-controller-service:2.0.5 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/download-controller-service:2.0.4 --help
+docker run -p 8080:8080 ghga/download-controller-service:2.0.5 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/dcs/openapi.yaml b/services/dcs/openapi.yaml
@@ -216,7 +216,7 @@ info:
     \ Object Storage. \n\nThis is an implementation of the DRS standard from the Global\
     \ Alliance for Genomics and Health, please find more information at: https://github.com/ga4gh/data-repository-service-schemas"
   title: Download Controller Service
-  version: 2.0.4
+  version: 2.0.5
 openapi: 3.1.0
 paths:
   /health:

diff --git a/services/dcs/pyproject.toml b/services/dcs/pyproject.toml
@@ -21,7 +21,7 @@ classifiers = [
     "Intended Audience :: Developers",
 ]
 name = "dcs"
-version = "2.0.4"
+version = "2.0.5"
 description = "Download Controller Service - a GA4GH DRS-compliant service for delivering files from S3 encrypted according to the GA4GH Crypt4GH standard."
 
 

diff --git a/services/ekss/README.md b/services/ekss/README.md
@@ -65,21 +65,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/encryption-key-store-service):
 ```bash
-docker pull ghga/encryption-key-store-service:1.4.2
+docker pull ghga/encryption-key-store-service:1.4.3
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/encryption-key-store-service:1.4.2 .
+docker build -t ghga/encryption-key-store-service:1.4.3 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/encryption-key-store-service:1.4.2 --help
+docker run -p 8080:8080 ghga/encryption-key-store-service:1.4.3 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/ekss/openapi.yaml b/services/ekss/openapi.yaml
@@ -219,7 +219,7 @@ info:
   description: A service managing storage and retrieval of symmetric keys in a HashiCorp
     Vault.
   title: Encryption Key Store Service
-  version: 1.4.2
+  version: 1.4.3
 openapi: 3.1.0
 paths:
   /health:

diff --git a/services/ekss/pyproject.toml b/services/ekss/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ekss"
-version = "1.4.2"
+version = "1.4.3"
 description = "Encryption Key Store Service - providing crypt4gh file secret extraction, storage and envelope generation"
 readme = "README.md"
 authors = [

diff --git a/services/fis/README.md b/services/fis/README.md
@@ -15,21 +15,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/file-ingest-service):
 ```bash
-docker pull ghga/file-ingest-service:4.0.0
+docker pull ghga/file-ingest-service:4.0.1
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/file-ingest-service:4.0.0 .
+docker build -t ghga/file-ingest-service:4.0.1 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/file-ingest-service:4.0.0 --help
+docker run -p 8080:8080 ghga/file-ingest-service:4.0.1 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/fis/openapi.yaml b/services/fis/openapi.yaml
@@ -108,7 +108,7 @@ info:
   description: A service to ingest s3 file upload metadata produced by thedata-steward-kit
     upload command
   title: File Ingest Service
-  version: 4.0.0
+  version: 4.0.1
 openapi: 3.1.0
 paths:
   /federated/ingest_metadata:

diff --git a/services/fis/pyproject.toml b/services/fis/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "fis"
-version = "4.0.0"
+version = "4.0.1"
 description = "File Ingest Service - A lightweight service to propagate file upload metadata to the GHGA file backend services"
 readme = "README.md"
 authors = [

diff --git a/services/ifrs/README.md b/services/ifrs/README.md
@@ -36,21 +36,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/internal-file-registry-service):
 ```bash
-docker pull ghga/internal-file-registry-service:2.0.3
+docker pull ghga/internal-file-registry-service:2.0.4
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/internal-file-registry-service:2.0.3 .
+docker build -t ghga/internal-file-registry-service:2.0.4 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/internal-file-registry-service:2.0.3 --help
+docker run -p 8080:8080 ghga/internal-file-registry-service:2.0.4 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/ifrs/pyproject.toml b/services/ifrs/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ifrs"
-version = "2.0.3"
+version = "2.0.4"
 description = "Internal File Registry Service - This service acts as a registry for the internal location and representation of files."
 readme = "README.md"
 authors = [

diff --git a/services/irs/README.md b/services/irs/README.md
@@ -14,21 +14,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/interrogation-room-service):
 ```bash
-docker pull ghga/interrogation-room-service:4.0.1
+docker pull ghga/interrogation-room-service:4.0.2
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/interrogation-room-service:4.0.1 .
+docker build -t ghga/interrogation-room-service:4.0.2 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/interrogation-room-service:4.0.1 --help
+docker run -p 8080:8080 ghga/interrogation-room-service:4.0.2 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/irs/pyproject.toml b/services/irs/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "irs"
-version = "4.0.1"
+version = "4.0.2"
 description = "Interrogation Room Service"
 readme = "README.md"
 authors = [

diff --git a/services/pcs/README.md b/services/pcs/README.md
@@ -26,21 +26,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/purge-controller-service):
 ```bash
-docker pull ghga/purge-controller-service:2.0.2
+docker pull ghga/purge-controller-service:2.0.3
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/purge-controller-service:2.0.2 .
+docker build -t ghga/purge-controller-service:2.0.3 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/purge-controller-service:2.0.2 --help
+docker run -p 8080:8080 ghga/purge-controller-service:2.0.3 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/pcs/openapi.yaml b/services/pcs/openapi.yaml
@@ -38,7 +38,7 @@ info:
   description: A service exposing an external API to commission file deletionsfrom
     the wholefile backend.
   title: Purge Controller Service
-  version: 2.0.2
+  version: 2.0.3
 openapi: 3.1.0
 paths:
   /files/{file_id}:

diff --git a/services/pcs/pyproject.toml b/services/pcs/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "pcs"
-version = "2.0.2"
+version = "2.0.3"
 description = "Purge Controller Service - a service to commission file deletions"
 readme = "README.md"
 authors = [

diff --git a/services/ucs/README.md b/services/ucs/README.md
@@ -15,21 +15,21 @@ We recommend using the provided Docker container.
 
 A pre-build version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/upload-controller-service):
 ```bash
-docker pull ghga/upload-controller-service:4.0.2
+docker pull ghga/upload-controller-service:4.0.3
 ```
 
 Or you can build the container yourself from the [`./Dockerfile`](./Dockerfile):
 ```bash
 # Execute in the repo's root dir:
-docker build -t ghga/upload-controller-service:4.0.2 .
+docker build -t ghga/upload-controller-service:4.0.3 .
 ```
 
 For production-ready deployment, we recommend using Kubernetes, however,
 for simple use cases, you could execute the service using docker
 on a single server:
 ```bash
 # The entrypoint is preconfigured:
-docker run -p 8080:8080 ghga/upload-controller-service:4.0.2 --help
+docker run -p 8080:8080 ghga/upload-controller-service:4.0.3 --help
 ```
 
 If you prefer not to use containers, you may install the service from source:

diff --git a/services/ucs/openapi.yaml b/services/ucs/openapi.yaml
@@ -433,7 +433,7 @@ info:
   description: A service managing uploads of file objects to an S3-compatible Object
     Storage.
   title: Upload Controller Service
-  version: 4.0.2
+  version: 4.0.3
 openapi: 3.1.0
 paths:
   /files/{file_id}:

diff --git a/services/ucs/pyproject.toml b/services/ucs/pyproject.toml
@@ -6,7 +6,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "ucs"
-version = "4.0.2"
+version = "4.0.3"
 description = "Upload Controller Service - manages uploads to an S3 inbox bucket."
 readme = "README.md"
 authors = [