Kibana version:

{
  "version": {
    "number": "7.11.0",
    "build_hash": "1a6d7308e58787bf0448f65c039739b40d4a6e3d",
    "build_number": 37074,
    "build_snapshot": true
  }
}

Elasticsearch version:

{
  "version": {
    "number": "7.11.0-SNAPSHOT",
    "build_flavor": "default",
    "build_type": "docker",
    "build_hash": "279bf21e59fcbac1135922b4828f82578f266234",
    "build_date": "2020-12-08T15:51:24.143094Z"
  }
}

Server OS version: Docker

Browser version: Firefox 83.0

Browser OS version: MacOS

Original install method (e.g. download page, yum, from source, etc.): Docker

Describe the bug:

Steps to reproduce:

1. Setup Fleet.
2. Install Palo Alto integration.
3. View the ingest node pipeline with
   GET _ingest/pipeline/logs-panw.panos-*
4. Find the script processor with several params.

Expected behavior:
The ingest node pipeline in Elasticsearch should contain numeric values for params. My assumption is that there's an issue with the YAML to JSON conversion, but I'm not sure. What I expect to see is this conversion output (where JSON has numbers).

Any additional context:

In this instance the incorrect data types cause problems within the Painless script. But this could cause problems elsewhere too. The error we see from this pipeline is

Cannot convert [java.lang.String] to an integral value.