[apm] update apm production package with correct var types

[jalvz]

Update APM production package with correct var types

Closes #1011

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Build Cause: Pull request #1012 opened

• Start Time: 2021-03-09T12:39:06.413+0000

• Duration: 17 min 42 sec

• Commit: 532fe9b

Test stats 🧪

Test	Results
Failed	0
Passed	60
Skipped	0
Total	60

Trends 🧪

[mtojek]

Please fill up the issue description justifying the PR.

Please link the appropriate Github issue.

[mtojek]

I understand that this is an acknowledged risk to push directly to production branch, right?

[jalvz]

Today I tried elastic-package following https://github.com/elastic/elastic-package#getting-started and that didn't work.

After running make build there is no integrations folder (can't cd integrations). I didn't have time to dig deeper, so I guess so. I will get back to it next week, didn't want to prevent my colleagues from testing with a prod package in the meanwhile.

[ycombinator]

Hey @jalvz, ++ for getting this PR in so your colleagues are unblocked. And thank you for trying out elastic-package. I see that the README has a step to cd integrations which obviously isn't generally applicable. I will fix the README now so it's clearer.

[ruflin]

To make a package available for testing, it is not required to be in the production branch, see table here: https://github.com/elastic/package-storage#package-storage

As soon as APM because a package that is installed by default pushing to production directly is very risky as it might affect all of Kibana. We should only do this as an exception.

[ycombinator]

I will fix the README now so it's clearer.

elastic/elastic-package#285