bump Helm chart to 3.6.2

eclipse-ditto · Nov 6, 2024 · e200990 · e200990
1 parent 24b3ff5
commit e200990
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git 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
@@ -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