Hexkit update (#112)

mephenor · web-flow · commit d770c351bbb8 · 2025-05-20T09:20:08.000+02:00
diff --git a/.pyproject_generation/pyproject_custom.toml b/.pyproject_generation/pyproject_custom.toml
@@ -6,7 +6,7 @@ dependencies = [
     "typer >= 0.15",
     "ghga-service-commons[api, auth, crypt] >= 4.1",
     "ghga-event-schemas >= 5.0",
-    "hexkit[akafka, s3, mongodb, opentelemetry] >= 5.0",
+    "hexkit[akafka, s3, mongodb, opentelemetry] >= 5.1.1",
     "crypt4gh >= 1.7",
     "hvac >= 2",
     "httpx >= 0.28",
diff --git a/lock/requirements-dev.txt b/lock/requirements-dev.txt
@@ -531,9 +531,9 @@ h11==0.16.0 \
     # via
     #   httpcore
     #   uvicorn
-hexkit==5.1.0 \
-    --hash=sha256:16cb52ea84ef00fe2d25cdbb1ae05d6a7023040e1e4978e51716a259e0759e86 \
-    --hash=sha256:4dc81925e09152449e7df211145d8f08ad78dc1cb4bf8074ba2eb5c47870e359
+hexkit==5.1.1 \
+    --hash=sha256:08be6279675c65ef4fcbab0a2d280f93ec0f427692c3d966d05f4afb600ba84d \
+    --hash=sha256:a548fc35e3c50bdd2c82941ce6288182db919daa6b65eb255d9ecb0a2135bc8b
     # via
     #   fsb (pyproject.toml)
     #   ghga-service-commons
@@ -711,7 +711,6 @@ opentelemetry-api==1.33.1 \
     --hash=sha256:4db83ebcf7ea93e64637ec6ee6fabee45c5cbe4abd9cf3da95c43828ddb50b83
     # via
     #   hexkit
-    #   opentelemetry-distro
     #   opentelemetry-exporter-otlp-proto-grpc
     #   opentelemetry-exporter-otlp-proto-http
     #   opentelemetry-instrumentation
@@ -724,10 +723,6 @@ opentelemetry-api==1.33.1 \
     #   opentelemetry-propagator-aws-xray
     #   opentelemetry-sdk
     #   opentelemetry-semantic-conventions
-opentelemetry-distro==0.54b1 \
-    --hash=sha256:009486513b32b703e275bb2f9ccaf5791676bbf5e2dcfdd90201ddc8f56f122b \
-    --hash=sha256:61d6b97bb7a245fddbb829345bb4ad18be39eb52f770fab89a127107fca3149f
-    # via hexkit
 opentelemetry-exporter-otlp==1.33.1 \
     --hash=sha256:4d050311ea9486e3994575aa237e32932aad58330a31fba24fdba5c0d531cf04 \
     --hash=sha256:9bcf1def35b880b55a49e31ebd63910edac14b294fd2ab884953c4deaff5b300
@@ -751,7 +746,6 @@ opentelemetry-instrumentation==0.54b1 \
     --hash=sha256:a4ae45f4a90c78d7006c51524f57cd5aa1231aef031eae905ee34d5423f5b198
     # via
     #   hexkit
-    #   opentelemetry-distro
     #   opentelemetry-instrumentation-aiokafka
     #   opentelemetry-instrumentation-asgi
     #   opentelemetry-instrumentation-botocore
@@ -798,7 +792,6 @@ opentelemetry-sdk==1.33.1 \
     --hash=sha256:85b9fcf7c3d23506fbc9692fd210b8b025a1920535feec50bd54ce203d57a531
     # via
     #   hexkit
-    #   opentelemetry-distro
     #   opentelemetry-exporter-otlp-proto-grpc
     #   opentelemetry-exporter-otlp-proto-http
 opentelemetry-semantic-conventions==0.54b1 \
diff --git a/lock/requirements.txt b/lock/requirements.txt
@@ -482,9 +482,9 @@ h11==0.16.0 \
     #   -c lock/requirements-dev.txt
     #   httpcore
     #   uvicorn
-hexkit==5.1.0 \
-    --hash=sha256:16cb52ea84ef00fe2d25cdbb1ae05d6a7023040e1e4978e51716a259e0759e86 \
-    --hash=sha256:4dc81925e09152449e7df211145d8f08ad78dc1cb4bf8074ba2eb5c47870e359
+hexkit==5.1.1 \
+    --hash=sha256:08be6279675c65ef4fcbab0a2d280f93ec0f427692c3d966d05f4afb600ba84d \
+    --hash=sha256:a548fc35e3c50bdd2c82941ce6288182db919daa6b65eb255d9ecb0a2135bc8b
     # via
     #   -c lock/requirements-dev.txt
     #   fsb (pyproject.toml)
@@ -620,7 +620,6 @@ opentelemetry-api==1.33.1 \
     # via
     #   -c lock/requirements-dev.txt
     #   hexkit
-    #   opentelemetry-distro
     #   opentelemetry-exporter-otlp-proto-grpc
     #   opentelemetry-exporter-otlp-proto-http
     #   opentelemetry-instrumentation
@@ -633,12 +632,6 @@ opentelemetry-api==1.33.1 \
     #   opentelemetry-propagator-aws-xray
     #   opentelemetry-sdk
     #   opentelemetry-semantic-conventions
-opentelemetry-distro==0.54b1 \
-    --hash=sha256:009486513b32b703e275bb2f9ccaf5791676bbf5e2dcfdd90201ddc8f56f122b \
-    --hash=sha256:61d6b97bb7a245fddbb829345bb4ad18be39eb52f770fab89a127107fca3149f
-    # via
-    #   -c lock/requirements-dev.txt
-    #   hexkit
 opentelemetry-exporter-otlp==1.33.1 \
     --hash=sha256:4d050311ea9486e3994575aa237e32932aad58330a31fba24fdba5c0d531cf04 \
     --hash=sha256:9bcf1def35b880b55a49e31ebd63910edac14b294fd2ab884953c4deaff5b300
@@ -670,7 +663,6 @@ opentelemetry-instrumentation==0.54b1 \
     # via
     #   -c lock/requirements-dev.txt
     #   hexkit
-    #   opentelemetry-distro
     #   opentelemetry-instrumentation-aiokafka
     #   opentelemetry-instrumentation-asgi
     #   opentelemetry-instrumentation-botocore
@@ -733,7 +725,6 @@ opentelemetry-sdk==1.33.1 \
     # via
     #   -c lock/requirements-dev.txt
     #   hexkit
-    #   opentelemetry-distro
     #   opentelemetry-exporter-otlp-proto-grpc
     #   opentelemetry-exporter-otlp-proto-http
 opentelemetry-semantic-conventions==0.54b1 \
diff --git a/pyproject.toml b/pyproject.toml
@@ -6,7 +6,7 @@ dependencies = [
     "typer >= 0.15",
     "ghga-service-commons[api, auth, crypt] >= 4.1",
     "ghga-event-schemas >= 5.0",
-    "hexkit[akafka, s3, mongodb, opentelemetry] >= 5.0",
+    "hexkit[akafka, s3, mongodb, opentelemetry] >= 5.1.1",
     "crypt4gh >= 1.7",
     "hvac >= 2",
     "httpx >= 0.28",
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-built version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/download-controller-service):
 ```bash
-docker pull ghga/download-controller-service:6.0.1
+docker pull ghga/download-controller-service:6.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/download-controller-service:6.0.1 .
+docker build -t ghga/download-controller-service:6.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/download-controller-service:6.0.1 --help
+docker run -p 8080:8080 ghga/download-controller-service:6.0.2 --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
@@ -206,7 +206,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: 6.0.1
+  version: 6.0.2
 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 = "6.0.1"
+version = "6.0.2"
 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-built 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:3.0.1
+docker pull ghga/encryption-key-store-service:3.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/encryption-key-store-service:3.0.1 .
+docker build -t ghga/encryption-key-store-service:3.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/encryption-key-store-service:3.0.1 --help
+docker run -p 8080:8080 ghga/encryption-key-store-service:3.0.2 --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
@@ -234,7 +234,7 @@ info:
   description: A service managing storage and retrieval of symmetric keys in a HashiCorp
     Vault.
   title: Encryption Key Store Service
-  version: 3.0.1
+  version: 3.0.2
 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 = "3.0.1"
+version = "3.0.2"
 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-built version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/file-ingest-service):
 ```bash
-docker pull ghga/file-ingest-service:8.0.1
+docker pull ghga/file-ingest-service:8.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/file-ingest-service:8.0.1 .
+docker build -t ghga/file-ingest-service:8.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/file-ingest-service:8.0.1 --help
+docker run -p 8080:8080 ghga/file-ingest-service:8.0.2 --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 the data-steward-kit
     upload command
   title: File Ingest Service
-  version: 8.0.1
+  version: 8.0.2
 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 = "8.0.1"
+version = "8.0.2"
 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-built 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:5.0.1
+docker pull ghga/internal-file-registry-service:5.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/internal-file-registry-service:5.0.1 .
+docker build -t ghga/internal-file-registry-service:5.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/internal-file-registry-service:5.0.1 --help
+docker run -p 8080:8080 ghga/internal-file-registry-service:5.0.2 --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 = "5.0.1"
+version = "5.0.2"
 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-built version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/interrogation-room-service):
 ```bash
-docker pull ghga/interrogation-room-service:6.0.1
+docker pull ghga/interrogation-room-service:6.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:6.0.1 .
+docker build -t ghga/interrogation-room-service:6.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:6.0.1 --help
+docker run -p 8080:8080 ghga/interrogation-room-service:6.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 = "6.0.1"
+version = "6.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-built version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/purge-controller-service):
 ```bash
-docker pull ghga/purge-controller-service:4.0.1
+docker pull ghga/purge-controller-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/purge-controller-service:4.0.1 .
+docker build -t ghga/purge-controller-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/purge-controller-service:4.0.1 --help
+docker run -p 8080:8080 ghga/purge-controller-service:4.0.2 --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: 4.0.1
+  version: 4.0.2
 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 = "4.0.1"
+version = "4.0.2"
 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-built version is available at [docker hub](https://hub.docker.com/repository/docker/ghga/upload-controller-service):
 ```bash
-docker pull ghga/upload-controller-service:6.0.1
+docker pull ghga/upload-controller-service:6.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/upload-controller-service:6.0.1 .
+docker build -t ghga/upload-controller-service:6.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/upload-controller-service:6.0.1 --help
+docker run -p 8080:8080 ghga/upload-controller-service:6.0.2 --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
@@ -417,7 +417,7 @@ info:
   description: A service managing uploads of file objects to an S3-compatible Object
     Storage.
   title: Upload Controller Service
-  version: 6.0.1
+  version: 6.0.2
 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 = "6.0.1"
+version = "6.0.2"
 description = "Upload Controller Service - manages uploads to an S3 inbox bucket."
 readme = "README.md"
 authors = [

Original file line number	Diff line number	Diff line change
`@@ -21,7 +21,7 @@ classifiers = [`
`21`	`21`	`"Intended Audience :: Developers",`
`22`	`22`	`]`
`23`	`23`	`name = "dcs"`
`24`		`-version = "6.0.1"`
	`24`	`+version = "6.0.2"`
`25`	`25`	`description = "Download Controller Service - a GA4GH DRS-compliant service for delivering files from S3 encrypted according to the GA4GH Crypt4GH standard."`
`26`	`26`
`27`	`27`