Separate building and packaging of Functionbeat by provider

[kvch]

From now on Functionbeat is separated into binaries based on cloud providers. This lead to the following naming changes:

• binary name: functionbeat-{provider}
• configuration name: functionbeat-{provider}.yml
• reference configuration name: functionbeat-{provider}.yml
• package names: functionbeat-{provider}-{version}-{platform}.{extension}
• index-pattern: functionbeat-{provider}-{version}-*
• ILM name: functionbeat-{provider}-{version}
• ILM rollover alias: functionbeat-{provider}-{version}

Packages are restructured to support building separately. Everything under x-pack/functionbeat/function is shared among all providers. On the same level, aws and local are the available provider packages.

Generated files, including fields.yml, configurations and fields.go, reside under the provider those belong to.

Binaries, configuration, etc. can be generated from the root of Functionbeat using mage as before. Running mage build|update|package|crossbuild runs and produces outputs under the providers folder. To set which provider you want to build for pass PROVIDERS env variable a comma-separated list of providers.

TODO

• fix E2E tests
• build/distributions?
• more testing

[kvch]

jenkins test this

[andrewkroh]

It would be nice if you could utilize as many of these common targets as possible:

	// mage:import
	_ "github.com/elastic/beats/dev-tools/mage/target/common"
	// mage:import
	//_ "github.com/elastic/beats/dev-tools/mage/target/build" # You can use this one because of the custom Build() target.
	// mage:import
	_ "github.com/elastic/beats/dev-tools/mage/target/pkg"
	// mage:import
	_ "github.com/elastic/beats/dev-tools/mage/target/dashboards"
	// mage:import
	_ "github.com/elastic/beats/dev-tools/mage/target/test"
	// mage:import
	"github.com/elastic/beats/dev-tools/mage/target/unittest"
	// mage:import
	"github.com/elastic/beats/dev-tools/mage/target/integtest"

[kvch]

How can I use target/build? I am not sure I understand your comment.