Merge branch 'main' into release-k8s-wisconsin

Author: kaitlynmichael

config.toml

@@ -55,7 +55,7 @@ rdi_redis_gears_version = "1.2.6"
 rdi_debezium_server_version = "2.3.0.Final"
 rdi_db_types = "cassandra|mysql|oracle|postgresql|sqlserver"
 rdi_cli_latest = "latest"
-rdi_current_version = "v1.6.2"
+rdi_current_version = "v1.6.3"
 
 [params.clientsConfig]
 "Python"={quickstartSlug="redis-py"}

content/integrate/redis-data-integration/installation/install-k8s.md

@@ -38,7 +38,7 @@ You can use this installation on [OpenShift](https://docs.openshift.com/) and ot
 including cloud providers' K8s managed clusters.
 
 You can pull the RDI images from the 
-[download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.2.tgz)
+[download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.3.tgz)
 or from your own [private image registry](#using-a-private-image-registry).
 
 ## Before you install
@@ -51,7 +51,7 @@ Complete the following steps before running Helm:
     [Access control]({{< relref "/operate/rs/security/access-control" >}}) for
     more information).
 -   Download the RDI helm chart tar file from the
-    [download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.2.tgz).
+    [download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.3.tgz).
 -   If you want to use a private image registry,
     [prepare it with the RDI images](#using-a-private-image-registry).
 
@@ -105,7 +105,7 @@ file as described below.
 ### Using a private image registry
 
 Add the RDI images from the
-[download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.2.tgz)
+[download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.3.tgz)
 to your local registry.
 The example below shows how to specify the registry and image pull secret in the
 [`values.yaml`](#the-valuesyaml-file) file for the Helm chart:

content/integrate/redis-data-integration/installation/install-vm.md

@@ -162,7 +162,7 @@ ufw allow 9121/tcp  # rdi-metric-exporter
 Follow the steps below for each of your VMs:
 
 1.  Download the RDI installer from the
-    [Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-1.6.2.tar.gz)
+    [Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-1.6.3.tar.gz)
     (from the *Modules, Tools & Integration* category) and extract it to your preferred installation
     folder.
 

content/integrate/redis-data-integration/installation/upgrade.md

@@ -23,8 +23,8 @@ Follow the steps below to upgrade an existing
 of RDI:
 
 1.  Download the RDI installer from the
-    [Redis download center](https://cloud.redis.io/#/rlec-downloads)
-    (under the *Modules, Tools & Integration* dropdown) and extract it to your
+    [Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-installation-1.6.3.tar.gz)
+    (in the *Modules, Tools & Integration* category) and extract it to your
     preferred installation folder.
 
 1.  Go to the installation folder:
@@ -97,7 +97,7 @@ installation of RDI:
     ```
 
 1.  Download the RDI helm chart tar file from the 
-    [Redis download center](https://cloud.redis.io/#/rlec-downloads).
+    [Redis download center](https://redis-enterprise-software-downloads.s3.amazonaws.com/redis-di/rdi-1.6.3.tgz).
 
 1.  Run the `helm upgrade` command:
     

content/integrate/redis-data-integration/release-notes/rdi-1-6-3.md

@@ -0,0 +1,31 @@
+---
+Title: Redis Data Integration release notes 1.6.3 (March 2025)
+alwaysopen: false
+categories:
+- docs
+- operate
+- rs
+description: Installation on Kubernetes with a Helm chart. Improvements for installation on VMs.
+linkTitle: 1.6.3 (March 2025)
+toc: 'true'
+weight: 989
+---
+
+> This maintenance release replaces the 1.6.2 release.
+
+RDI’s mission is to help Redis customers sync Redis Enterprise with live data from their slow disk-based databases to:
+
+- Meet the required speed and scale of read queries and provide an excellent and predictable user experience.
+- Save resources and time when building pipelines and coding data transformations.
+- Reduce the total cost of ownership by saving money on expensive database read replicas.
+
+RDI keeps the Redis cache up to date with changes in the primary database, using a [_Change Data Capture (CDC)_](https://en.wikipedia.org/wiki/Change_data_capture) mechanism.
+It also lets you _transform_ the data from relational tables into convenient and fast data structures that match your app's requirements. You specify the transformations using a configuration system, so no coding is required.
+
+## Headlines
+
+- Fix: RDI 1.6.2 VM Installer not working on RHEL-8 OS.
+
+## Limitations
+
+RDI can write data to a Redis Active-Active database. However, it doesn't support writing data to two or more Active-Active replicas. Writing data from RDI to several Active-Active replicas could easily harm data integrity as RDI is not synchronous with the source database commits.

content/operate/rs/references/rest-api/requests/actions/_index.md

@@ -23,7 +23,7 @@ weight: $weight
 GET /v1/actions
 ```
 
-Get the status of all actions (executing, queued, or completed) on all entities (clusters, nodes, and databases). This API tracks long-lived API requests that return either a `task_id` or an `action_uid`.
+Get the status of all running, pending, or completed actions on all clusters, nodes, and databases. This API tracks long-lived API requests that return either a `task_id` or an `action_uid`.
 
 #### Required permissions
 
@@ -41,7 +41,18 @@ GET /v1/actions
 
 ### Response {#get-all-response}
 
-Returns a JSON array of [action objects]({{< relref "/operate/rs/references/rest-api/objects/action" >}}) and an array of [state-machine objects]({{< relref "/operate/rs/references/rest-api/objects/state-machine" >}}).
+Returns a JSON array of [action objects]({{< relref "/operate/rs/references/rest-api/objects/action" >}}), which represent tasks, and an array of [state-machine objects]({{< relref "/operate/rs/references/rest-api/objects/state-machine" >}}).
+
+| Field | Type/Value | Description |
+|-------|------------|-------------|
+| action_uid | string | The action's globally unique identifier |
+| name | string | Name of the running or failed state machine |
+| progress | float (range: 0-100) | Percent of completed steps for the action |
+| status | "pending"<br />"active"<br />"completed"<br />"failed" | The action's status |
+| node_uid | string | UID of the node where the operation runs (optional) |
+| object_name | string | The object that the action runs on (optional) |
+| state | string | The current state of the state machine (optional)  |
+| pending_ops | JSON object | List of operations that are waiting to run (optional)<br />{{<code>}}"pending_ops": {<br />  "3": {<br />    "heartbeat": integer,<br />    "snapshot": { ... },<br />    "last_sample_time": integer,<br />    "op_name": string,<br />    "status_code": string,<br />    "status_description": string,<br />    "progress": float<br />  }<br />}{{</code>}}<br />`pending_ops` is a map where the key is the `shard_id`, and the value is a map that can include the following optional fields:<br />**heartbeat**: The time, in seconds since the Unix epoch, since the last change in the progress of the operation.<br />**snapshot**: A map of properties stored by the operation that are needed to run.<br />**last_sample_time**: The time, in seconds since the Unix epoch, when the last snapshot of the operation was taken.<br />**op_name**: The name of the operation from the state machine that is running.<br />**status_code**: The code for the operation's current status.<br />**status_description**: The operation's current status.<br />**progress**: The operation's progress in percentage (1 to 100). |
 
 Regardless of an action’s source, each action in the response contains the following attributes: `name`, `action_uid`, `status`, and `progress`.
 
@@ -93,7 +104,7 @@ Regardless of an action’s source, each action in the response contains the fol
 GET /v1/actions/{uid}
 ```
 
-Get the status of a currently executing, queued, or completed action.
+Get the status of a specific action.
 
 #### Required permissions
 
@@ -119,6 +130,17 @@ GET /v1/actions/{uid}
 
 Returns an [action object]({{< relref "/operate/rs/references/rest-api/objects/action" >}}).
 
+| Field | Type/Value | Description |
+|-------|------------|-------------|
+| action_uid | string | The action's globally unique identifier |
+| name | string | Name of the running or failed state machine |
+| progress | float (range: 0-100) | Percent of completed steps for the action |
+| status | "pending"<br />"active"<br />"completed"<br />"failed" | The action's status |
+| node_uid | string | UID of the node where the operation runs (optional) |
+| object_name | string | The object that the action runs on (optional) |
+| state | string | The current state of the state machine (optional)  |
+| pending_ops | JSON object | List of operations that are waiting to run (optional)<br />{{<code>}}"pending_ops": {<br />  "3": {<br />    "heartbeat": integer,<br />    "snapshot": { ... },<br />    "last_sample_time": integer,<br />    "op_name": string,<br />    "status_code": string,<br />    "status_description": string,<br />    "progress": float<br />  }<br />}{{</code>}}<br />`pending_ops` is a map where the key is the `shard_id`, and the value is a map that can include the following optional fields:<br />**heartbeat**: The time, in seconds since the Unix epoch, since the last change in the progress of the operation.<br />**snapshot**: A map of properties stored by the operation that are needed to run.<br />**last_sample_time**: The time, in seconds since the Unix epoch, when the last snapshot of the operation was taken.<br />**op_name**: The name of the operation from the state machine that is running.<br />**status_code**: The code for the operation's current status.<br />**status_description**: The operation's current status.<br />**progress**: The operation's progress in percentage (1 to 100). |
+
 Regardless of an action’s source, each action contains the following attributes: `name`, `action_uid`, `status`, and `progress`.
 
 #### Example JSON body