-
Notifications
You must be signed in to change notification settings - Fork 25.3k
Remove flavor from build #85796
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 flavor from build #85796
Conversation
The default distribution is the only remaining build flavor, and has been for quite a while now. This commit removes flavor from the internal Build class. It keeps rest api compat for nodes info for now by hardcoding `default`.
Pinging @elastic/es-delivery (Team:Delivery) |
Pinging @elastic/es-core-infra (Team:Core/Infra) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question, otherwise LGTM.
@@ -225,7 +225,7 @@ public void execute(List<PluginDescriptor> plugins) throws Exception { | |||
terminal.println(logPrefix + "Installing " + pluginId); | |||
try { | |||
if ("x-pack".equals(pluginId)) { | |||
handleInstallXPack(buildFlavor()); | |||
throw new UserException(ExitCodes.CONFIG, "this distribution of Elasticsearch contains X-Pack by default"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we even need to handle this anymore at this point. The "x-pack" plugin hasn't been a thing for many versions. I assume this was only added to ease migration after x-pack was folded into ES.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a fair point, but I would like to think about that separately. We certainly might get users who have used ES before trying to install x-pack, though at some point we should definitely remove this.
case "oss": | ||
return Flavor.OSS; | ||
case "unknown": | ||
return Flavor.UNKNOWN; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do we use for the integ-test distribution? Was this "unknown" before?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes it would have been unknown, though I don't think it matters, since nothing will be checking it now.
The default distribution is the only remaining build flavor, and has been for
quite a while now. This commit removes flavor from the internal Build
class. It keeps rest api compat for nodes info for now by hardcoding
default
.