Merge branch 'main' into DOC-4639

Author: rrelledge

.github/workflows/rc_api_sync.yaml

@@ -0,0 +1,70 @@
+name: rc_api_sync
+
+on:
+  schedule:
+    - cron: '0 0 * * *' # run every day at midnight UTC time
+  workflow_dispatch: # or run on manual trigger
+
+jobs:
+  rc_api_sync:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+      actions: write
+    steps:
+      - name: 'Checkout'
+        uses: 'actions/checkout@v3'
+
+      - name: 'Fetch openapi json file'
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          branch="rc_api_sync"
+          spec_change=false
+
+          # check if remote branch already exists
+          git fetch --all
+          set +e
+          git ls-remote --exit-code --heads origin "refs/heads/${branch}"
+          if [ "$?" -eq 0 ]; then
+            set -e
+            # if it does, create local branch off existing remote branch
+            git checkout -b "${branch}" "origin/${branch}"
+            git branch --set-upstream-to="origin/${branch}" "${branch}"
+            git pull
+          else
+            set -e
+            # otherwise, create local branch from main
+            git checkout -b "${branch}"
+          fi
+
+          curl -Ls https://api.redislabs.com/v1/cloud-api-docs \
+            | jq '(.. | .example? | try select(test("^{"))) |= fromjson' > content/operate/rc/api/api-reference/openapi.json
+
+          spec_is_different=$(git diff content/operate/rc/api/api-reference/openapi.json)
+
+          if [[ ! -z $spec_is_different ]]; then
+            spec_change=true
+
+            git add "content/operate/rc/api/api-reference/openapi.json"
+            git config user.email "177626021+redisdocsapp[bot]@users.noreply.github.com"
+            git config user.name "redisdocsapp[bot]"
+            git commit -m "Update content/operate/rc/api/api-reference/openapi.json"
+          fi
+
+          if [ "$spec_change" = true ] ; then
+            git push origin "${branch}"
+
+            # If a pr is not already open, create one
+            set +e
+            gh search prs -R redis/docs --state open --match title "update rc openapi spec" | grep -q "update rc openapi spec"
+            if [ "$?" -eq 1 ]; then
+              set -e
+              gh pr create \
+                --body "update rc openapi spec" \
+                --title "update rc openapi spec" \
+                --head "$branch" \
+                --base "main"
+            fi
+          fi

content/apis/_index.md

@@ -45,7 +45,7 @@ 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](https://api.redislabs.com/v1/swagger-ui.html)
+- [Redis Cloud REST API reference]({{< relref "/operate/rc/api/api-reference" >}})
 
 
 ### Redis Enterprise Software API

content/commands/bitpos/index.md

@@ -104,16 +104,25 @@ Non-existent keys are treated as empty strings.
 
 ## Examples
 
-{{% redis-cli %}}
-SET mykey "\xff\xf0\x00"
-BITPOS mykey 0
-SET mykey "\x00\xff\xf0"
-BITPOS mykey 1 0
-BITPOS mykey 1 2
-BITPOS mykey 1 2 -1 BYTE
-BITPOS mykey 1 7 15 BIT
-set mykey "\x00\x00\x00"
-BITPOS mykey 1
-BITPOS mykey 1 7 -3 BIT
-{{% /redis-cli %}}
-
+```redis
+redis> SET mykey "\xff\xf0\x00"
+OK
+redis> BITPOS mykey 0
+(integer) 12
+redis> SET mykey "\x00\xff\xf0"
+OK
+redis> BITPOS mykey 1 0
+(integer) 8
+redis> BITPOS mykey 1 2
+(integer) 16
+redis> BITPOS mykey 1 2 -1 BYTE
+(integer) 16
+redis> BITPOS mykey 1 7 15 BIT
+(integer) 8
+redis> set mykey "\x00\x00\x00"
+OK
+redis> BITPOS mykey 1
+(integer) -1
+redis> BITPOS mykey 1 7 -3 BIT
+(integer) -1
+```

content/commands/client-list/index.md

@@ -114,6 +114,8 @@ Here is the meaning of the fields:
 * `user`: the authenticated username of the client
 * `redir`: client id of current client tracking redirection
 * `resp`: client RESP protocol version. Added in Redis 7.0
+* `rbp`: peak size of the client's read buffer since the client connected. Added in Redis 7.0
+* `rbs`: current size of the client's read buffer in bytes. Added in Redis 7.0
 
 The client flags can be a combination of:
 

content/commands/latency-histogram/index.md

@@ -54,9 +54,9 @@ Each histogram consists of the following fields:
   * Each bucket represents a latency range
   * Each bucket covers twice the previous bucket's range
   * Empty buckets are excluded from the reply
-  * The tracked latencies are between 1 microsecond and roughly 1 second
+  * The tracked latencies are between 1 nanosecond and roughly 1 second
   * Everything above 1 second is considered +Inf
-  * At max, there will be log2(1,000,000,000)=30 buckets
+  * At max, there will be log2(1,000,000,000) = 30 buckets
 
 This command requires the extended latency monitoring feature to be enabled, which is the default.
 If you need to enable it, call `CONFIG SET latency-tracking yes`.

content/develop/tools/insight/release-notes/v.2.64.0.md

@@ -0,0 +1,33 @@
+---
+Title: Redis Insight v2.64.0, December 2024
+linkTitle: v2.64.0 (December 2024)
+date: 2024-12-19 00:00:00 +0000
+description: Redis Insight v2.64
+weight: 1
+
+---
+## 2.64 (December 2024)
+This is the General Availability (GA) release of Redis Insight 2.64.
+
+### Highlights 
+- Improved the database connections list and simplified the connection form, delivering a cleaner, more intuitive UI for improved focus.
+- New in-app reminders to prevent your free Redis Cloud database from being deleted due to inactivity, ensuring you can make the most of it to test your ideas.
+
+### Details
+
+**Features and improvements**
+- [#4088](https://github.com/RedisInsight/RedisInsight/pull/4088), [#4078](https://github.com/RedisInsight/RedisInsight/pull/4078), [#4094](https://github.com/RedisInsight/RedisInsight/pull/4094) Improved the database connections list and simplified the connection form, delivering a cleaner, more intuitive UI for improved focus.
+- [#4189](https://github.com/RedisInsight/RedisInsight/pull/4189), [#4191](https://github.com/RedisInsight/RedisInsight/pull/4191) New in-app reminders notify you before your free Redis Cloud database is deleted due to inactivity, ensuring you can make the most of it to test your ideas.
+- [#4204](https://github.com/RedisInsight/RedisInsight/pull/4204), [#4196](https://github.com/RedisInsight/RedisInsight/pull/4196), [#4202](https://github.com/RedisInsight/RedisInsight/pull/4202) Various vulnerabilities have been fixed.
+
+**Bugs**
+- [#4194](https://github.com/RedisInsight/RedisInsight/pull/4194) Resolved an [issue](https://github.com/RedisInsight/RedisInsight/issues/4186) where modifying a JSON value inadvertently converted strings into numbers.
+
+**SHA-256 Checksums**
+| Package | SHA-256 |
+|--|--|
+| Windows | iYZbKsFtz/Ua4qeBdeHIRtZRiA1I50R3yY1t3VUD2cn94EpZLR5Xz3lK3yRxA85PxJaHjrWljyGliZv0OX0KBg== |
+| Linux AppImage | ToEFW8wVLI8oFoc/puzf2Cwoff8gBTsIxEsGjQRZq5D5BgrE3muxtuEQto3J2RiRbadGAZx6AZPh75WVJ0DKRw== |
+| Linux Debian| /k6jgfzDSRJ0yWmbtxpD5WG2i9wGUZ4r2AexDz6rUOLyZMqQPJUKEKuonprFvHZp+PUW/EtSWc436IFykBVmsQ== |
+| MacOS Intel | PrbRc+ju0UKxr4huP7Xl9Sq0fH0XaxUtydW86rAYepEAADUADsAYV2lB8gO7Ohs9ukJ7mXBEU7OJWRqJGLhxHg== |
+| MacOS Apple silicon | E6kTbnkoW3eji/v7WVrnwqlEKk444+hxiFqt56r8J+zAHhmX9dlNd7y37xdJlQ82FZ9QOIIMsN5Z0N+bgRisuw== |

content/develop/tools/redis-for-vscode/release-notes/v1.2.0.md

@@ -0,0 +1,35 @@
+---
+Title: Redis for VS Code v1.2.0, December 2024
+linkTitle: v1.2.0 (December 2024)
+date: 2024-12-19 00:00:00 +0000
+description: Redis for VS Code v1.2
+weight: 99
+---
+
+## 1.2.0 (December 2024)
+
+This is the General Availability (GA) release of Redis for VS Code 1.2.
+
+### Headlines
+* Work with keys across multiple database indexes, which are automatically discovered and displayed in the database list.
+* Support for adding multiple elements to the head or tail of Redis lists, for both new and existing keys.
+* Auto-refresh the list of keys and key values with a customizable timer.
+* Delete and update previously added CA and client certificates to keep them updated.
+
+### Details
+
+- [#223](https://github.com/RedisInsight/Redis-for-VS-Code/pull/223) Work with keys across multiple database indexes. Database indexes with keys are automatically discovered and displayed in the database list. 
+- [#207](https://github.com/RedisInsight/Redis-for-VS-Code/pull/207) Support for adding multiple elements to the head or tail of Redis lists for new and existing key.
+- [#226](https://github.com/RedisInsight/Redis-for-VS-Code/pull/226) Auto-refresh the list of keys and key values with a customizable timer. To do so, enable the Auto-refresh mode by clicking the control next to the Refresh button and setting the refresh rate.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Ability to delete previously added CA and Client certificates to keep them up-to-date.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Enhanced both the Java and PHP serialized formatters: the Java formatter now supports date and time data, while the PHP formatter includes UTF-8 encoding for better handling of special characters and multi-language data.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Keep databases and the list of keys [expanded](https://github.com/RedisInsight/Redis-for-VS-Code/issues/217) after navigating away.
+- [#226](https://github.com/RedisInsight/Redis-for-VS-Code/pull/226) New users can optionally encrypt sensitive data, such as connection certificates and passwords. Existing users can enable encryption by deleting the ~/.redis-for-vscode/redisinsight.db file and re-adding their database connections.
+
+**Bugs**
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Resolved an issue where large integers in JSON keys were being rounded, ensuring data integrity.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Saved SNI and SSH connection information for newly added database connections.
+- [#224](https://github.com/RedisInsight/Redis-for-VS-Code/pull/224) Fixed an issue to display multiple hash fields when expanding a hash value.
+
+### Get started with Redis for VS Code
+Install the extension from the [Visual Studio Code Marketplace](https://marketplace.visualstudio.com/items?itemName=redis.redis-for-vscode) to use it.

content/develop/use/patterns/distributed-locks.md

@@ -56,7 +56,6 @@ already available that can be used for reference.
 * [ScarletLock](https://github.com/psibernetic/scarletlock) (C# .NET implementation with configurable datastore).
 * [Redlock4Net](https://github.com/LiZhenNet/Redlock4Net) (C# .NET implementation).
 * [node-redlock](https://github.com/mike-marcacci/node-redlock) (NodeJS implementation). Includes support for lock extension.
-* [simple-redis-mutex](https://github.com/AmrSaber/simple-redis-mutex) (Node.js implementation) Available as an [NPM package](https://www.npmjs.com/package/simple-redis-mutex).
 * [Deno DLM](https://github.com/oslabs-beta/Deno-Redlock) (Deno implementation)
 * [Rslock](https://github.com/hexcowboy/rslock) (Rust implementation). Includes async and lock extension support.
 

content/embeds/rc-create-db-first-steps.md

@@ -8,15 +8,4 @@ To create a database in your Redis Cloud account:
 
     {{<image filename="images/rc/button-database-new.png" alt="The New Database button creates a new database." width="120px">}}
 
-    This displays the **Create database** screen.
-
-3. Select your Redis use case. There are four pre-defined use cases:
-
-    {{<image filename="images/rc/create-database-redis-use-cases.png" alt="The Redis Use case panel">}}
-
-    - **Cache**: Stores short-term or volatile data. Can be used for session management, semantic cache, session store, and other uses where data is short-lived.
-    - **Database**: Stores durable and consistent data. Can be used for document databases, feature storage, gaming leaderboards, durable caches, and other uses where your data needs to be highly available and persistent.
-    - **Vector search**: Manages and manipulates vector data. Can be used for Generative AI, recommendation systems, visual search, and other uses where you can search and query your data.
-    - **Custom**: If your Redis use case doesn't match any of the other use cases, you can choose this option to customize all of your settings.
-
-    Select the use case that best matches your Redis use case. You can always change the settings later. 
+    This displays the **Create database** screen.

content/embeds/rc-create-db-use-cases.md

@@ -0,0 +1,10 @@
+3. Select your Redis use case. There are four pre-defined use cases:
+
+    {{<image filename="images/rc/create-database-redis-use-cases.png" alt="The Redis Use case panel">}}
+
+    - **Cache**: Stores short-term or volatile data. Can be used for session management, semantic cache, session store, and other uses where data is short-lived.
+    - **Database**: Stores durable and consistent data. Can be used for document databases, feature storage, gaming leaderboards, durable caches, and other uses where your data needs to be highly available and persistent.
+    - **Vector search**: Manages and manipulates vector data. Can be used for Generative AI, recommendation systems, visual search, and other uses where you can search and query your data.
+    - **Custom**: If your Redis use case doesn't match any of the other use cases, you can choose this option to customize all of your settings.
+
+    Select the use case that best matches your Redis use case. You can always change the settings later.