plugin functional capabilities in xpack

[stacey-gammon]

Just like we have plugin_functional folder in OSS, I think it would be good to have in xpack as well. I'd like to showcase/test some of the advanced capabilities.

[elasticmachine]

Pinging @elastic/kibana-operations

[stacey-gammon]

@spalger - do you know what level of effort this would be? I think we'll need this for some of the data access stuff, as async will be in x-pack and I'd like to build some sample demos on top of the async code.

[stacey-gammon]

Although... if one runs with yarn start --plugin-path sample/plugin if the license isn't trial and the sample plugin is dependent on an x-pack plugin... that should just naturally work. Although I think for functional testing, it runs as oss, not trial license.

[spalger]

Adding plugin_functional tests shouldn't be too hard, but first we have to get the plugin_functional tests working again which keeps falling off my TODO list (fixing that).

Not sure what you mean by you last comment, but if a plugin requires x-pack and us loaded into OSS Kibana, the server won't start because the dependency isn't met. yarn start runs with x-pack included by default, and the license level is set by Elasticsearch which is basic by default, so unless the stuff you're looking to test required a higher license level they should work. Either way, we have flags we can pass to Elasticsearch when it starts to run it as a trial license for functional testing.

[stacey-gammon]

Looks like this will be fixed by #51994 🎉

[jbudz]

Closing this out with #51994 merged