Fix base fields in ECS file

[ruflin]

So far the base fields of ECS were not read as they were nested under base. This brings them to the top level and resolves all the conflicts with field definitions in libbeat and other Beats.

Moving forward we must find a better way for writing the ECS file to Beats as this step has to be done manually each time.

[andrewkroh]

Should/could we change how the fields.yml file in elastic/ecs is generated to make it match this format?

[webmat]

The current fields.yml file is a simple concatenation of all of the different field definition files. ECS has more keys in there, which are ECS specific.

So we'll likely need to put together a script that strips out these keys and produces what Beats expects...

Would it make sense to have this script live in Beats, since it's an adaptation of the schema to Beats?

[webmat]

LGTM

It looks like the Jenkins failure is due to capacity issues over there.

[webmat]

The current fields.yml file is a simple concatenation of all of the different field definition files. ECS has more keys in there, which are ECS specific.

So we'll likely need to put together a script that strips out these keys and produces what Beats expects...

Would it make sense to have this script live in Beats, since it's an adaptation of the schema to Beats?

[ruflin]

I'm actually thinking to adjust the ECS fields.yml but need to figure out why. I think the two should be in sync.

[ruflin]

I created a follow up issue for the discussion around the structure unification. elastic/ecs#292