No need to whitelist known fields

elastic · Jul 16, 2021 · 7e399a3 · 7e399a3
1 parent db098dc
commit 7e399a3
Showing 1 changed file with 0 additions and 3 deletions.
diff --git a/...st_pipelines/public/application/components/pipeline_editor/context/processors_context.tsx b/...st_pipelines/public/application/components/pipeline_editor/context/processors_context.tsx
@@ -153,12 +153,9 @@ export const PipelineProcessorsContextProvider: FunctionComponent<Props> = ({
           // These are the option names we get back from our UI
           const knownOptionNames = [
             ...Object.keys(processorTypeAndOptions.options),
-
             // We manually add fields that we **don't** want to be treated as "unknownOptions"
             'internal_networks',
             'internal_networks_field',
-            'transport',
-            'iana_number',
           ];
 
           // The processor that we are updating may have options configured the UI does not know about