Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove requirement that new platform plugins in the repo specify a version #34660

Closed
epixa opened this issue Apr 5, 2019 · 1 comment
Closed
Labels
Feature:New Platform Feature:Plugins stale Used to mark issues that were closed for being stale Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc

Comments

@epixa
Copy link
Contributor

epixa commented Apr 5, 2019

Plugins in the Kibana repo are versioned alongside Kibana itself, so there's no reason to require them to specify a version in their manifest. It might be challenging to remove this requirement in the legacy world, but at the very least we should do it for new platform plugins.

Plugins not in the repo will still need to specify a version for now.

@epixa epixa added Feature:Plugins Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc Feature:New Platform labels Apr 5, 2019
@elasticmachine
Copy link
Contributor

Pinging @elastic/kibana-platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature:New Platform Feature:Plugins stale Used to mark issues that were closed for being stale Team:Core Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants