Create NP plugin boilerplate script

[lizozom]

Summary

Added an option to the yarn kbn script to create plugin boiler plate code.

yarn kbn plugin new_plugin --ui --server (It's possible to set only one option, but at least one is mandatory)

This command will create a new plugin (unless a plugin with that name already exists) having the following structure:

new_plugin

• common
  • index.ts
• public (if --ui is set)
  • index.ts
  • types.ts
  • plugins.ts
• server (if --server is set)
  • index.ts
  • plugin.ts
• kibana.json
• README.md

It also adds the plugin to i18nrc.json

If the script fails to initialize the plugin, it attempts to perform cleanup.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• This was checked for cross-browser compatibility, including a check against IE11
• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[joshdover]

Seems like a lot of overlap between this and the plugin generator in packages/kbn-plugin-generator. That package has not been updated for New Platform plugins though and is a bit more targetted to 3rd party development.

@lizozom what do you think about updating the existing generator?

[elasticmachine]

💔 Build Failed

• continuous-integration/kibana-ci/pull-request
• Commit: 1ec739f

History

• 💔 Build #14802 failed 824bfd15b5a5478cc7ef47dd00d858ea9f300d25

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[lukeelmers]

+1 for considering an update to the existing generator, especially since historically we've documented it as the recommended way to bootstrap a new plugin.

On another note - whichever route we go, we should also be sure everything aligns with our CONVENTIONS.md to prevent confusion.

[lizozom]

@joshdover @lukeelmers - will move the code over there

[lizozom]

Replaced by #55281