Add _xpack endpoint options in the Console UI

[elasticmachine]

Original comment by @elasticmachine:

Blocked by LINK REDACTED

Original comment by @bohyun-e:

from discuss: https://discuss.elastic.co/t/add-xpack-endpoint-options-in-console/57877

we can use X-Pack API's to perform various operations.
For example few of them are listed below:-
GET _xpack/security/user
GET _xpack/security/role
GET _xpack/
GET _xpack/watcher/stats
DELETE /_xpack/security/user/test
DELETE /_xpack/security/role/test
For _xpack endpoints, there are no suggestions available within the Console.

[elasticmachine]

Original comment by @ycombinator:

At the moment there is no good way for plugins to, well, plug in additional API endpoints into Console. So some changes will need to be made to the Console core code first.

[elasticmachine]

Original comment by @skearns64:

When we do this, we should include Watcher API stuff, too.

I wonder if there would be any issues simply adding these to the OSS knowledge base (the database of typeahead things)?

I agree that pluggability is probably best, so x-pack and other things in the future can add their own items to the KB, but I would imagine it makes things a bit more complex.

[elasticmachine]

Original comment by @ycombinator:

I wonder if there would be any issues simply adding these to the OSS knowledge base (the database of typeahead things)?

I think it would result in a (mildly) bad UX if a user could typeahead an API call but then get an error back because that API endpoint doesn't actually exist.

Also, since anyone can create plugins, where would we draw the line on which plugins' APIs are included in Console autocomplete vs. not? It would appear that we are drawing the line at plugins authored by Elastic; could this be perceived negatively by the OSS community?

[elasticmachine]

Original comment by @skearns64:

Both are good points! I revoke my question :)

[elasticmachine]

Original comment by @skearns64:

I'd like to revisit this, now that we're building the Watcher UI, which would really benefit from this kind of typeahead support. There is a PR that was opened against Sense (elastic/sense#95) to add this support.

cc @epixa @kevinkluge @jbudz @tylersmalley - Do we still feel that the Console knowledge base should not contain typeahead support for Watcher, and that we would need to build in extensibility to Console before adding this sort of capability?

[elasticmachine]

Original comment by @epixa:

Yeah, we really need to make console pluginable in order to support plugin APIs like those provided by xpack.

[cjcenizal]

This has been addressed by #17769 and #19928.