Elasticsearch Windows MSI package

Summary

This is an experimental status issue, documenting known remaining tasks before Elasticsearch is ready to move to GA as part of Elastic Stack Installers. This repository contains MSI package build framework (ElastiBuild) capable of discovering various artifacts from local file system and artifacts API, fetching, unpacking and building supported MSI packages.

• Support building and testing Elasticsearch MSI within ElastiBuild framework.

Below we outline a high level plan of changes that will help us achieve the above goals:

• Internal refactoring of ElastiBuild Package Compiler projects
• Support for parsing, fetching and unpacking Elasticsearch-specific artifact names (vs Beats and Kibana)
• Evaluate options and decide on implementation for running Elasticsearch as Windows Service
• Implement running Elasticsearch as Windows Service and appropriate installer support

Note to self: https://github.com/elastic/elasticsearch-net-abstractions

Relevant User Requests, Issues and Potential Improvements:

• MSI package doesn't upgrade log4j2.properties file
  MSI package doesn't upgrade log4j2.properties file windows-installers#351
• Specify License file
  ES MSI Enable security settings, license installation and TLS windows-installers#277
  Specify a license file to apply when starting Elasticsearch as part of installation windows-installers#126
• The uninstaller won't work if heap size is changed in settings to more than 1/2 manually
  The uninstaller won't work if heap size is changed in settings to more than 1/2 manually. windows-installers#244
• Configure ML node role
  MSI - Configure ML node role windows-installers#194
• Computing Space requirements based on chosen plugins
  Computing Space requirements based on chosen plugins windows-installers#11
• Support configuration file as a PROPERTY
  Support configuration file as a PROPERTY windows-installers#46
• Change in xpack.{basic-feature}.enabled setting
  Change in xpack.{basic-feature}.enabled setting #66

Hi @jasontedor , I created this ticket in Elasticsearch per email thread from @colings86 :

Thanks for all the progress made on this so far. We now have the following:
Beta
- Task Management API (issue #51628 created)
- Windows MSI Installer (Owner - @ygel  - Can we create an issue for this please?)
- GeoSQL (issue #48521 created)```

I was wondering why this was transferred here?

[jasontedor]

I'm not sure that I understand why this issue is best placed in the elastic/elasticsearch repository? It seems that all the work you're describing would be done in this repository?

I believe the point was to keep these in a single place. Maybe Colin can chime in?
And yes, all the work is in this repo.

[colings86]

I think we should have this issue wherever it makes sense for the feature which in this case seems to be this repo. The important thing from my point of view is that:

1. We have an public issue somewhere that people can go to see what needs to be done to get a feature to GA
2. We link to the issue from the documentation so our users can see what is currently keeping a feature in beta/experimental

Thanks @ygel for creating this issue

Thank you @colings86, sounds good to me!