Include licensed field in PluginInfo xcontent and toString #65830
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pugnascotia
added
>non-issue
:Core/Infra/Plugins
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
…ield-in-plugininfo-xcontent-tostring
pugnascotia
deleted the
incude-licensed-field-in-plugininfo-xcontent-tostring
branch
Contributor
Author
|
Backported to 7.x in 7995c79 |
pugnascotia
added a commit
that referenced
this pull request
Dec 8, 2020
When #65409 was merged, it didn't include the new PluginInfo field licensed in the toString() or toXContent() outputs. This PR adds them and updates the tests accordingly.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When #65409 was merged, it didn't include the new
PluginInfofieldlicensedin thetoString()ortoXContent()outputs. This PR adds them and updates the tests accordingly.