Merge branch 'main' into release-rs-fuya-fuya

Author: rrelledge

content/apis/_index.md

@@ -45,13 +45,13 @@ Redis Cloud is a fully managed Database as a Service offering and the fastest wa
 
 - [Redis Cloud REST API introduction]({{< relref "/operate/rc/api/" >}})
 - [Redis Cloud REST API examples]({{< relref "/operate/rc/api/examples/" >}})
-- [Redis Cloud REST API reference]({{< relref "/operate/rs/references/rest-api/" >}})
+- [Redis Cloud REST API reference](https://api.redislabs.com/v1/swagger-ui.html)
 
 
 ### Redis Enterprise Software API
 If you have installed Redis Enterprise Software, you can automate operations with the Redis Enterprise REST API.
 
-- [Redis Enterprise Software REST API introduction]({{< relref "/operate/rc/api/" >}})
+- [Redis Enterprise Software REST API introduction]({{< relref "/operate/rs/references/rest-api/" >}})
 - [Redis Enterprise Software REST API requests]({{< relref "/operate/rs/references/rest-api/requests/" >}})
 - [Redis Enterprise Software REST API objects]({{< relref "/operate/rs/references/rest-api/objects/" >}})
 

content/develop/connect/insight/_index.md

@@ -92,9 +92,15 @@ The CLI is accessible at any time within the application.
 
 ### Workbench
 
-Advanced command line interface with intelligent command auto-complete and complex data visualizations.
+Workbench is an advanced command line interface with intelligent command auto-complete and complex data visualization support.
 * Built-in guides: you can conveniently discover Redis and Redis Stack features using the built-in guides.
 * Command auto-complete support for all features in Redis and Redis Stack.
+* Advanced, schema-aware auto-complete for Redis Query Engine, which provides for faster query building with context-sensitive suggestions that recognize indexes, schemas, and fields based on your current query. Start typing any Redis Query Engine command in to try this feature. See below for an example of an in-progress `FT.SEARCH` command.
+
+<img src="images/Workbench_Search.png">
+
+Workbench also includes:
+
 * Visualizations of your indexes, queries, and aggregations.
 * Visualizations of your [time series]({{< relref "/develop/data-types/timeseries/" >}}) data.
 

content/develop/connect/insight/images/Workbench_Search.png

@@ -0,0 +1,25 @@
+---
+Title: Redis Insight v2.60.0, October 2024
+linkTitle: v2.60.0 (October 2024)
+date: 2024-10-30 00:00:00 +0000
+description: Redis Insight v2.60
+weight: 1
+
+---
+## 2.60 (October 2024)
+This is the General Availability (GA) release of Redis Insight 2.60.
+
+### Highlights
+- Advanced and schema-aware command auto-complete for [Redis Query Engine](https://redis.io/docs/latest/develop/interact/search-and-query/?utm_source=redisinsight&utm_medium=main&utm_campaign=release_notes) is now available in Workbench, enabling faster and more accurate query building with smart suggestions for indexes, schemas, and expressions.
+- Support for adding multiple elements to the head or tail of lists, for both new or existing keys.
+- Multiple UI enhancements for clarity and ease of use when editing Redis Data Integration (RDI) jobs.
+
+### Details
+
+**Features and improvements**
+- [#3553](https://github.com/RedisInsight/RedisInsight/pull/3553), [#3647](https://github.com/RedisInsight/RedisInsight/pull/3647), [#3669](https://github.com/RedisInsight/RedisInsight/pull/3669) Advanced, schema-aware auto-complete for [Redis Query Engine](https://redis.io/docs/latest/develop/interact/search-and-query/?utm_source=redisinsight&utm_medium=main&utm_campaign=release_notes) in Workbench. Enjoy faster query building with context-sensitive suggestions that recognize indexes, schemas, and fields based on your current query. Start typing any [Redis Query Engine](https://redis.io/docs/latest/commands/?group=search) command in Workbench to try this feature. 
+- [#3891](https://github.com/RedisInsight/RedisInsight/pull/3891) Allows to easily push multiple elements to the head or tail of list data types, whether creating new or updating existing lists.
+- [#3891](https://github.com/RedisInsight/RedisInsight/pull/3891) UX/UI enhancements to provide more details about Redis Data Integration (RDI) job transformation and output results in the dry-run section.
+- [#3981](https://github.com/RedisInsight/RedisInsight/pull/3981) Removes confirmation prompts for template insertions in Redis Data Integration jobs, simplifying a workflow.
+- [#3827](https://github.com/RedisInsight/RedisInsight/pull/3827) Provides easy-to-understand metrics of network input/output by automatically converting units in Browser Overview.
+- [#3982](https://github.com/RedisInsight/RedisInsight/pull/3982), [#3975](https://github.com/RedisInsight/RedisInsight/pull/3975), [#3941](https://github.com/RedisInsight/RedisInsight/pull/3941) Various vulnerabilities have been fixed.

content/develop/connect/insight/release-notes/v.2.60.0.md

@@ -164,7 +164,7 @@ Checking for an element is O(K) or O(K*n) for stacked filters, where n is the nu
 
 ## Academic sources
 - [Space/Time Trade-offs in Hash Coding with Allowable Errors](http://www.dragonwins.com/domains/getteched/bbc/literature/Bloom70.pdf) by Burton H. Bloom.
-- [Scalable Bloom Filters](https://haslab.uminho.pt/cbm/files/dbloom.pdf)
+- [Scalable Bloom Filters](https://gsd.di.uminho.pt/members/cbm/ps/dbloom.pdf)
 
 ## References
 ### Webinars

content/develop/data-types/probabilistic/bloom-filter.md

@@ -190,7 +190,7 @@ More info: [Overview of kubectl](https://kubernetes.io/docs/reference/kubectl/ov
 {{%definition "Lightweight Directory Access Protocol (LDAP)"%}}
 A protocol for accessing and maintaining distributed directory services over an IP network, often used to authenticate users.
 
-More info: [LDAP wikipedia](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol/), [LDAP authentication]({{<relref "/operate/rs/security/access-control/ldap">}})
+More info: [LDAP wikipedia](https://en.wikipedia.org/wiki/Lightweight_Directory_Access_Protocol), [LDAP authentication]({{<relref "/operate/rs/security/access-control/ldap">}})
 {{%/definition%}}
 
 ## M - O {#letter-m}

content/glossary/_index.md

@@ -136,14 +136,29 @@ traffic. The diagram below shows this configuration:
 
 {{< image filename="images/rdi/ingest/ingest-active-passive-vms.png" >}}
 
+See [Install on VMs]({{< relref "/integrate/redis-data-integration/installation/install-vm" >}})
+for more information.
+
 ### RDI on Kubernetes
 
-You can run RDI in a namespace on your own Kubernetes cluster with
-a separate deployment for each of the control plane
-components (REST API, operator, and metrics exporter). The operator
-creates and configures deployments for the collector and stream processor
-when you start a pipeline from the CLI tool. This means that you must
-provide the operator with a service account that has permissions to create and manipulate pods in the namespace. 
+You can use the RDI [Helm chart](https://helm.sh/docs/topics/charts/) to install
+on [Kubernetes (K8s)](https://kubernetes.io/), including Red Hat
+[OpenShift](https://docs.openshift.com/). This creates:
+
+-   A K8s [namespace](https://kubernetes.io/docs/concepts/overview/working-with-objects/namespaces/) named `rdi`.
+-   [Deployments](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/) for the 
+    [RDI operator]({{< relref "/integrate/redis-data-integration/architecture#how-rdi-is-deployed" >}}),
+    [metrics exporter]({{< relref "/integrate/redis-data-integration/observability" >}}), and API server.
+-   A [service account](https://kubernetes.io/docs/concepts/security/service-accounts/) along with a
+    [role](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#restrictions-on-role-creation-or-update)
+    and [role binding](https://kubernetes.io/docs/reference/access-authn-authz/rbac/#rolebinding-and-clusterrolebinding) for the RDI operator.
+-   A [Configmap](https://kubernetes.io/docs/concepts/configuration/configmap/)
+    for the different components with RDI Redis database details.
+-   [Secrets](https://kubernetes.io/docs/concepts/configuration/secret/)
+    with the RDI Redis database credentials and TLS certificates.
+
+See [Install on Kubernetes]({{< relref "/integrate/redis-data-integration/installation/install-k8s" >}})
+for more information.
 
 ### Secrets and security considerations
 

content/integrate/redis-data-integration/architecture.md

@@ -328,81 +328,11 @@ find the preparation guides for the databases that RDI supports in the
 [Prepare source databases]({{< relref "/integrate/redis-data-integration/data-pipelines/prepare-dbs" >}})
 section.
 
-## Set secrets
-
-Before you deploy your pipeline, you must set the authentication secrets for the
-source and target databases. Each secret has a corresponding property name that
-you can pass to the
-[`redis-di set-secret`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-set-secret" >}})
-command to set the property's value. You can then refer to these properties
-in `config.yaml` using the syntax "`${PROPERTY_NAME}`"
-(the sample [config.yaml file](#the-configyaml-file) shows these properties in use).
-For example, you would use the
-following command line to set the source database username to `myUserName`:
-
-```bash
-redis-di set-secret SOURCE_DB_USERNAME myUserName
-```
-
-The table below shows the property name for each secret. Note that the
-username and password are required for the source and target, but the other
-secrets are only relevant to TLS/mTLS connections.
-
-| Property name | Description |
-| :-- | :-- |
-| `SOURCE_DB_USERNAME` | Username for the source database |
-| `SOURCE_DB_PASSWORD` | Password for the source database |
-| `SOURCE_DB_CACERT` | (For TLS only) Source database trust certificate |
-| `SOURCE_DB_KEY` | (For mTLS only) Source database private key |
-| `SOURCE_DB_CERT` | (For mTLS only) Source database public key |
-| `SOURCE_DB_KEY_PASSWORD` | (For mTLS only) Source database private key password |
-| `TARGET_DB_USERNAME` | Username for the target database |
-| `TARGET_DB_PASSWORD` | Password for the target database |
-| `TARGET_DB_CACERT` | (For TLS only) Target database trust certificate |
-| `TARGET_DB_KEY` | (For mTLS only) Target database private key |
-| `TARGET_DB_CERT` | (For mTLS only) Target database public key |
-| `TARGET_DB_KEY_PASSWORD` | (For mTLS only) Target database private key password |
-
 ## Deploy a pipeline
 
-If you are hosting RDI on your own VMs, you can use the
-[`deploy`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-deploy" >}})
-command to deploy a configuration, including the jobs, once you have created them.
-
-If your RDI CLI is deployed as a pod in a Kubernetes cluster, you should perform the following
-steps to deploy a pipeline:
-
-- Create a [ConfigMap](https://kubernetes.io/docs/concepts/configuration/configmap/) from the
-  YAML files in your `jobs` folder:
-
-  ```bash
-  kubectl create configmap redis-di-jobs --from-file=jobs/
-  ```
-
-- Deploy your jobs:
-
-  ```bash
-  kubectl exec -it pod/redis-di-cli -- redis-di deploy
-  ```
-
-{{< note >}}When you create or modify a ConfigMap, it will be available in the `redis-di-cli` pod
-after a short delay. Wait around 30 seconds before running the `redis-di deploy` command.{{< /note >}}
-
-You have two options to update the ConfigMap:
-
-- For smaller changes, you can edit the ConfigMap directly with this command:
-
-  ```bash
-  kubectl edit configmap redis-di-jobs
-  ```
-
-- For bigger changes, such as adding another job file, edit the files in your local `jobs` folder and then run this command:
-
-  ```bash
-  kubectl create configmap redis-di-jobs --from-file=jobs/ --dry-run=client -o yaml | kubectl apply -f -
-  ```
-
-{{< note >}} You must run `kubectl exec -it pod/redis-di-cli -- redis-di deploy` after updating the ConfigMap with either option.{{< /note >}}
+When your configuration is ready, you must deploy it to start using the pipeline. See
+[Deploy a pipeline]({{< relref "/integrate/redis-data-integration/data-pipelines/deploy" >}})
+to learn how to do this.
 
 ## Ingest pipeline lifecycle
 

content/integrate/redis-data-integration/data-pipelines/data-pipelines.md

@@ -0,0 +1,67 @@
+---
+Title: Deploy a pipeline
+aliases: /integrate/redis-data-integration/ingest/data-pipelines/data-type-handling/
+alwaysopen: false
+categories:
+- docs
+- integrate
+- rs
+- rdi
+description: Learn how to deploy an RDI pipeline
+group: di
+linkTitle: Deploy
+summary: Redis Data Integration keeps Redis in sync with the primary database in near
+  real time.
+type: integration
+weight: 2
+---
+
+The sections below explain how to deploy a pipeline after you have created the required
+[configuration]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines" >}}).
+
+## Set secrets
+
+Before you deploy your pipeline, you must set the authentication secrets for the
+source and target databases. Each secret has a corresponding property name that
+you can pass to the
+[`redis-di set-secret`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-set-secret" >}})
+command to set the property's value. You can then refer to these properties
+in `config.yaml` using the syntax "`${PROPERTY_NAME}`"
+(the sample [config.yaml file](#the-configyaml-file) shows these properties in use).
+For example, you would use the
+following command line to set the source database username to `myUserName`:
+
+```bash
+redis-di set-secret SOURCE_DB_USERNAME myUserName
+```
+
+The table below shows the property name for each secret. Note that the
+username and password are required for the source and target, but the other
+secrets are only relevant to TLS/mTLS connections.
+
+| Property name | Description |
+| :-- | :-- |
+| `SOURCE_DB_USERNAME` | Username for the source database |
+| `SOURCE_DB_PASSWORD` | Password for the source database |
+| `SOURCE_DB_CACERT` | (For TLS only) Source database trust certificate |
+| `SOURCE_DB_KEY` | (For mTLS only) Source database private key |
+| `SOURCE_DB_CERT` | (For mTLS only) Source database public key |
+| `SOURCE_DB_KEY_PASSWORD` | (For mTLS only) Source database private key password |
+| `TARGET_DB_USERNAME` | Username for the target database |
+| `TARGET_DB_PASSWORD` | Password for the target database |
+| `TARGET_DB_CACERT` | (For TLS only) Target database trust certificate |
+| `TARGET_DB_KEY` | (For mTLS only) Target database private key |
+| `TARGET_DB_CERT` | (For mTLS only) Target database public key |
+| `TARGET_DB_KEY_PASSWORD` | (For mTLS only) Target database private key password |
+
+## Deploy a pipeline
+
+When you have created your configuration, including the [jobs]({{< relref "/integrate/redis-data-integration/data-pipelines/data-pipelines#job-files" >}}), use the
+[`redis-di deploy`]({{< relref "/integrate/redis-data-integration/reference/cli/redis-di-deploy" >}})
+command to deploy them:
+
+```bash
+redis-di deploy --dir <path to pipeline folder>
+```
+
+You can also deploy a pipeline using [Redis Insight]({{< relref "/develop/connect/insight/rdi-connector" >}}).

content/integrate/redis-data-integration/data-pipelines/deploy.md

@@ -37,7 +37,11 @@ and then run the following commands:
 1.  Grant the required permissions to the user:
 
     ```sql
+    # MySQL <v8.0
     mysql> GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'user' IDENTIFIED BY 'password';
+
+    # MySQL v8.0 and above
+    mysql> GRANT SELECT, RELOAD, SHOW DATABASES, REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'user'@'localhost';
     ```
 
 1.  Finalize the user's permissions: