From 41df0b9ec71a8daa68916c5acaf75b162f3f939e Mon Sep 17 00:00:00 2001 From: Jon Jackson Date: Mon, 8 Dec 2025 11:52:59 -0500 Subject: [PATCH] Fix editing secrets with mixed text and binary data (OCPBUGS-62611) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit When a secret contained both text and binary values, the edit form would fail due to a runtime error. The stringData initialization was returning null when any binary field was detected, breaking text field handling. Now binary fields are skipped during stringData initialization while text fields are preserved, allowing proper editing of mixed-type secrets. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude --- .../components/secrets/create-secret/SecretFormWrapper.tsx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/frontend/public/components/secrets/create-secret/SecretFormWrapper.tsx b/frontend/public/components/secrets/create-secret/SecretFormWrapper.tsx index faeb72e6971..9eedd7150ca 100644 --- a/frontend/public/components/secrets/create-secret/SecretFormWrapper.tsx +++ b/frontend/public/components/secrets/create-secret/SecretFormWrapper.tsx @@ -60,7 +60,7 @@ export const SecretFormWrapper: FCC = (props) => { const [stringData, setStringData] = useState( Object.entries(props.obj?.data ?? {}).reduce>((acc, [key, value]) => { if (isBinary(null, Buffer.from(value, 'base64'))) { - return null; + return acc; } acc[key] = value ? Base64.decode(value) : ''; return acc;