fix: omit elasticsearch field for policy update API (#121412) (#123368)

Although this field is returned in the GET response, we do not allow it to be set through the policy update API, so it must be omitted first. Originally fixed in #119131. Co-authored-by: ogupte <[email protected]> Co-authored-by: ogupte <[email protected]> Co-authored-by: Mark Hopkin <[email protected]>
elastic · Jan 19, 2022 · 34b82cc · 34b82cc
1 parent abe0f62
commit 34b82cc
Showing 1 changed file with 2 additions and 1 deletion.
diff --git a/.../fleet/public/applications/fleet/sections/agent_policy/edit_package_policy_page/index.tsx b/.../fleet/public/applications/fleet/sections/agent_policy/edit_package_policy_page/index.tsx
@@ -389,7 +389,8 @@ export const EditPackagePolicyForm = memo<{
   const [formState, setFormState] = useState<PackagePolicyFormState>('INVALID');
   const savePackagePolicy = async () => {
     setFormState('LOADING');
-    const result = await sendUpdatePackagePolicy(packagePolicyId, packagePolicy);
+    const { elasticsearch, ...restPackagePolicy } = packagePolicy; // ignore 'elasticsearch' property since it fails route validation
+    const result = await sendUpdatePackagePolicy(packagePolicyId, restPackagePolicy);
     setFormState('SUBMITTED');
     return result;
   };