From 30cf86f922b4e3aee7cf1e1322eba39d3c1f95c9 Mon Sep 17 00:00:00 2001
From: Tobias Krause <tobiaskrause@users.noreply.github.com>
Date: Tue, 20 Dec 2022 09:35:39 +0100
Subject: [PATCH] Apache Kafka scaler: move partition limitation feature to the
 correct version (#1020)

---
 content/docs/2.10/scalers/apache-kafka.md | 2 ++
 content/docs/2.8/scalers/apache-kafka.md  | 2 --
 content/docs/2.9/scalers/apache-kafka.md  | 2 ++
 3 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/content/docs/2.10/scalers/apache-kafka.md b/content/docs/2.10/scalers/apache-kafka.md
index d12ee9220..2ded7dd9c 100644
--- a/content/docs/2.10/scalers/apache-kafka.md
+++ b/content/docs/2.10/scalers/apache-kafka.md
@@ -33,6 +33,7 @@ triggers:
     scaleToZeroOnInvalidOffset: false
     excludePersistentLag: false
     version: 1.0.0
+    partitionLimitation: '1,2,10-20,31'
 ```
 
 **Parameter list:**
@@ -50,6 +51,7 @@ If 'false' (the default), the scaler will keep a single consumer for that partit
 partition will be scaled to zero. See the [discussion](https://github.com/kedacore/keda/issues/2612) about this parameter.
 - `excludePersistentLag` - When set to `true`, the scaler will exclude partition lag for partitions which current offset is the same as the current offset of the previous polling cycle. This parameter is useful to prevent scaling due to partitions which current offset message is unable to be consumed. If `false` (the default), scaler will include all consumer lag in all partitions as per normal. (Default: `false`, Optional)
 - `version` - Version of your Kafka brokers. See [samara](https://github.com/Shopify/sarama) version (Default: `1.0.0`, Optional)
+- `partitionLimitation` - Comma separated list of partition ids to scope the scaling on. Allowed patterns are "x,y" and/or ranges "x-y". If set, the calculation of the lag will only take these ids into account.  (Default: All partitions, Optional)
 
 > **Note:**
 >
diff --git a/content/docs/2.8/scalers/apache-kafka.md b/content/docs/2.8/scalers/apache-kafka.md
index a69493a89..a8197feaf 100644
--- a/content/docs/2.8/scalers/apache-kafka.md
+++ b/content/docs/2.8/scalers/apache-kafka.md
@@ -32,7 +32,6 @@ triggers:
     allowIdleConsumers: false
     scaleToZeroOnInvalidOffset: false
     version: 1.0.0
-    partitionLimitation: '1,2,10-20,31'
 ```
 
 **Parameter list:**
@@ -49,7 +48,6 @@ partitions on a topic, allowing for idle consumers. (Default: `false`, Optional)
 If 'false' (the default), the scaler will keep a single consumer for that partition. Otherwise ('true'), the consumers for that
 partition will be scaled to zero. See the [discussion](https://github.com/kedacore/keda/issues/2612) about this parameter.
 - `version` - Version of your Kafka brokers. See [samara](https://github.com/Shopify/sarama) version (Default: `1.0.0`, Optional)
-- `partitionLimitation` - Comma separated list of partition ids to scope the scaling on. Allowed patterns are "x,y" and/or ranges "x-y". If set, the calculation of the lag will only take these ids into account.  (Default: All partitions, Optional) 
 
 > **Note:**
 >
diff --git a/content/docs/2.9/scalers/apache-kafka.md b/content/docs/2.9/scalers/apache-kafka.md
index d12ee9220..2ded7dd9c 100644
--- a/content/docs/2.9/scalers/apache-kafka.md
+++ b/content/docs/2.9/scalers/apache-kafka.md
@@ -33,6 +33,7 @@ triggers:
     scaleToZeroOnInvalidOffset: false
     excludePersistentLag: false
     version: 1.0.0
+    partitionLimitation: '1,2,10-20,31'
 ```
 
 **Parameter list:**
@@ -50,6 +51,7 @@ If 'false' (the default), the scaler will keep a single consumer for that partit
 partition will be scaled to zero. See the [discussion](https://github.com/kedacore/keda/issues/2612) about this parameter.
 - `excludePersistentLag` - When set to `true`, the scaler will exclude partition lag for partitions which current offset is the same as the current offset of the previous polling cycle. This parameter is useful to prevent scaling due to partitions which current offset message is unable to be consumed. If `false` (the default), scaler will include all consumer lag in all partitions as per normal. (Default: `false`, Optional)
 - `version` - Version of your Kafka brokers. See [samara](https://github.com/Shopify/sarama) version (Default: `1.0.0`, Optional)
+- `partitionLimitation` - Comma separated list of partition ids to scope the scaling on. Allowed patterns are "x,y" and/or ranges "x-y". If set, the calculation of the lag will only take these ids into account.  (Default: All partitions, Optional)
 
 > **Note:**
 >