Cherry-pick elastic#8836 to 6.5: Make sure that packages.yml use the …

…same files definition (elastic#9103)

Cherry-pick of PR elastic#8836 to 6.5 branch. Original message: 

This PR make sure the definition style used by the packages.yml and the custom
function packages.yml match.

Temporary fix for dashboards under 7.0 (elastic#9031)

As some of libbeat fields were renamed in 7.0, currently a few dashboards break that depend on this fields. Adding an alias for the old fields is to temporarly fix this. As soon as the ECS migration is done, fields in the dashboard have to be renamed. Hopefully this can happen in an automated way.

Revert "Minor Journalbeat fixes and additions (elastic#8973) (elastic…

…#9006)" (elastic#9011)

This reverts commit e1c3e0e.

Cherry-pick elastic#8769 to 6.4: The 'export config' subcommand shoul…

…d display field reference instead of values (elastic#8832)

Cherry-pick of PR elastic#8769 to 6.4 branch. Original message:

Change the behavior of the export config to not display the values from
the keystore or the environment.

Set CFLAGS for Packetbeat arm64 cross-compile (elastic#7809) (elastic…

…#8409)

Cross-building Packetbeat was failing because the appropriate CFLAGS were not being set.

(cherry picked from commit 9796ec9)

Bump version to 5.6.13 (elastic#8327)

Document the use of `make release` instead of `make package` (elastic…

…#8187) (elastic#8304)

The `package` Makefile target was removed and replaced by the `release` and `snapshot` targets.

(cherry picked from commit 19f7dd3)

Bump docs version for 5.6.11 (elastic#8026)

Fix changelog entry (elastic#8001) (elastic#8003)

(cherry picked from commit 8e4fd66)

Fix filebeat registry meta being nil vs empty (elastic#7632) (elastic…

…#7644)

Filebeat introduces a meta field to registry entries in 6.3.1. The meta field is used to distuingish different log streams in docker files. For other input types the meta field must be null. Unfortunately the input loader did initialize the meta field with an empty dictionary. This leads to failing matches of old and new registry entries. Due to the match failing, old entries will not be removed, and filebeat will handle all files as new files on startup (old logs are send again).

Users will observe duplicate entries in the reigstry file. One entry with "meta": null and one entry with "meta": {}. The entry with "meta": {} will be used by filebeat. The null-entry will not be used by filebeat, but is kept in the registry file, cause it has now active owner (yet).

Improvements provided by this PR:

* when matching states consider an empty map and a null-map to be equivalent
* update input loader to create a null map for old state -> registry entries will be compatible on upgrade
* Add checks in critical places replacing an empty map with a null-map
* Add support to fix registry entries on load. states from corrupted 6.3.1 files will be merged into one single state on load
* introduce unit tests for loading different registry formats
* introduce system tests validating output and registry when upgrading filebeat from an older version

Closes: elastic#7634

(cherry picked from commit c558984)