Enabled editing of the host field for existing Redis connections

[CristianoGuilloux]

What

Enabled editing of the host field for existing Redis connections in the manual connection edit flow.

Previously, host was hidden in edit mode for regular connections and Sentinel connections, which forced users to recreate or clone a connection when the endpoint changed. This update exposes the host input during editing while keeping the existing restrictions for cloud-managed connections and Azure connections that are intentionally read-only.

The change also updates the related form tests to cover the new edit behavior and to confirm the Azure/non-Azure restrictions still behave correctly.

Testing

Automation:

Ran redisinsight/ui/src/pages/home/components/manual-connection/manual-connection-form/ManualConnectionFrom.spec.tsx
Ran redisinsight/ui/src/pages/home/components/manual-connection/ManualConnectionWrapper.spec.tsx
Results:

ManualConnectionFrom.spec.tsx: 42 tests passed
ManualConnectionWrapper.spec.tsx: 8 tests passed
Manual:

Built a Windows installer from this fork and verified the app packages successfully with the change included.

Recording.2026-04-07.082857.mp4

---

Note

Medium Risk
Enables modifying the connection host during edit flows, which affects how existing instances are updated and could lead to misconfigured endpoints if validation/regressions exist. Changes are limited to UI form field visibility/readonly behavior plus test updates.

Overview
Manual connection edit flows now expose the host field for editing (previously hidden), including in Sentinel edit mode; host remains hidden/blocked for cloud-managed connections.

Azure behavior is preserved but adjusted: the host input is now rendered and disabled (along with other connection fields) instead of being absent, and tests were updated/added to cover editing host and the Azure vs non-Azure readonly rules.

^{Reviewed by Cursor Bugbot for commit e68bc94. Bugbot is set up for automated code reviews on this repo. Configure here.}

[CLAassistant]

All committers have signed the CLA.

[jit-ci]

Hi, I’m Jit, a friendly security platform designed to help developers build secure applications from day zero with an MVS (Minimal viable security) mindset.

In case there are security findings, they will be communicated to you as a comment inside the PR.

Hope you’ll enjoy using Jit.

Questions? Comments? Want to learn more? Get in touch with us.

[valkirilov]

Thank you for your contribution @CristianoGuilloux, it makes sense to let people edit the host of their database, but we need to discuss this with the team - whether your request for a change is enough, or we have to amend the UI a little bit more.

In the meantime, you can always fall back to the Clone functionality, which lets you "update" the HOST (yes, for the price of having duplicates, of course), but at least you don't have to enter all the rest of the credentials.