From 36367744242d173c270db6dab87aa2a4977e4ef8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Thomas=20J=C3=A4ckle?= Date: Wed, 6 Nov 2024 08:18:15 +0100 Subject: [PATCH] bump Helm chart to 3.6.2 --- deployment/helm/ditto/Chart.yaml | 2 +- deployment/helm/ditto/values.yaml | 6 +++--- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/deployment/helm/ditto/Chart.yaml b/deployment/helm/ditto/Chart.yaml index c828c289b7..8b7210cbef 100644 --- a/deployment/helm/ditto/Chart.yaml +++ b/deployment/helm/ditto/Chart.yaml @@ -17,7 +17,7 @@ description: | (real world “Things”, e.g. devices like sensors, smart heating, connected cars, smart grids, EV charging stations etc). type: application version: 3.6.2 # chart version is effectively set by release-job -appVersion: 3.6.1 +appVersion: 3.6.2 keywords: - iot-chart - digital-twin diff --git a/deployment/helm/ditto/values.yaml b/deployment/helm/ditto/values.yaml index c8f5ce3196..eb4567d00b 100644 --- a/deployment/helm/ditto/values.yaml +++ b/deployment/helm/ditto/values.yaml @@ -723,7 +723,7 @@ policies: # Configuring this to high values will reduce the need to query MongoDB too often - it should however be aligned # with the amount of `creditsPerBatch` issued per `interval` - in order to avoid long running queries. readsPerQuery: 100 - # readsPerQuery configures the number of documents to delete for each credit. + # writesPerCredit configures the number of documents to delete for each credit. # If for example one entity would have 1000 journal entries to cleanup, a `writes-per-credit` of 100 would lead # to 10 delete operations performed against MongoDB. writesPerCredit: 100 @@ -987,7 +987,7 @@ things: # Configuring this to high values will reduce the need to query MongoDB too often - it should however be aligned # with the amount of `creditsPerBatch` issued per `interval` - in order to avoid long running queries. readsPerQuery: 100 - # readsPerQuery configures the number of documents to delete for each credit. + # writesPerCredit configures the number of documents to delete for each credit. # If for example one entity would have 1000 journal entries to cleanup, a `writes-per-credit` of 100 would lead # to 10 delete operations performed against MongoDB. writesPerCredit: 100 @@ -1608,7 +1608,7 @@ connectivity: # Configuring this to high values will reduce the need to query MongoDB too often - it should however be aligned # with the amount of `creditsPerBatch` issued per `interval` - in order to avoid long running queries. readsPerQuery: 100 - # readsPerQuery configures the number of documents to delete for each credit. + # writesPerCredit configures the number of documents to delete for each credit. # If for example one entity would have 1000 journal entries to cleanup, a `writes-per-credit` of 100 would lead # to 10 delete operations performed against MongoDB. writesPerCredit: 100