-
Notifications
You must be signed in to change notification settings - Fork 150
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
Add plugin deprecation info into registry index file #228
Conversation
It would be useful to see examples of script work in both cases - for non-deprecated and for deprecated plugins. |
Also please consider changing index.json items model in README.md https://github.com/eclipse/che-plugin-registry#get-index-list-of-all-plugins |
@sleshchenko I had described it in the description, but yes, an example would be even better. |
As about readme, we have already described the |
So, but README.md does not give any clue that |
@sleshchenko updated |
Signed-off-by: Mykola Morhun <[email protected]>
Signed-off-by: Mykola Morhun [email protected]
What does this PR do?
Adds
deprecate
section of plugin meta information intoindex.json
file of the plugin registry.If a plagin is not deprecated then nothing will be changed in current model.
If a plugin is deprecated then to its metadata in the registry
index.json
file will be addeddeprecate
section, which is copy ofdeprecate
section of the pluginmeta.yaml
file.For example:
This change is needed for dashboard to be able to display deprecation on a plugin and suggest auto migration. See eclipse-che/che#13021