ToDo

[ghost]

TODOs

• Build any beat from cli using packages from artifacts-api.
• Add beat-specific icon to show up in Add/Remove Programs and MSI.
• Support for x86 and x64 msi build workflows.
• Fix quiet install failure (/q, /qn, /q+).
• Fix administrative install failure (/a).
• Add support for all build target - builds all known installers. 4cbc102
• Grab short description of a beat from its README.md file. Dependency removed in 92fa202.
• Cache used ProductId (guid) -> version map in config.yaml. Deferred.
• Evaluate switching to "SDK-style" project format for XXXCompiler projects.
• Create meta-ticket for installer test proces. Connect with Beats team and discuss testing and CI engagement. See Installer Wiki
• Evaluate using elastic/elasticsearch-net-abstractions to talk to artifacts-api. Elasticsearch Windows MSI package #59
• Add support for latest, signifying latest version of the artifact (container).
  Might not be trivial: https://github.com/elastic/infra/issues/14645, https://github.com/elastic/infra/issues/5193, Elasticsearch latest not available elasticsearch-docker#215 (comment) No action
• Figure out when to remove the hard-link so that package can be removed from disk. d518199. No Action: existing cleanup behavior removes links.
• Convert TODO entries to Github issues.

Converted to tickets:

• Implement CLI shim for beats (and ES/Kibana later) to run from any directory using same configuration file as service. Add CLI shim that reads same configuration files as Windows sevice #10
• Implement package signing. Add env var support for package signing. Implement package signing. #14
• After install (UI sequence) provide means to open/edit config file. Let user know what to do next after install is complete #40
• Notify Beats team that installer build process depends on beat's README.md file contents, specifically line 3, containing beat description. Discuss alternatives to make it less brittle. README.md dependency removed in 92fa202, others remain, see Installer dependencies on metadata in Beats repository #4.
• Configure assembly versions properly for build runner and per-package compilers. Configure assembly versions for build runner and per-package compilers to follow unified release versions #9
• Evaluate possibility of specifying external, pre-written beat-specific .yaml config (filebeat, winlogbeat, etc) file to be picked up by Beats installers. It can be on file system or pulled from GIthub for example. Canned configuration files #11
• Evaluate WixSharp's ManagedProject approach as potential v2. It provides much improved UI .customization options, custom action handling then then some. Look into WixSharp.ManagedProject #12
• Evaluate possibility of migrating existing configuration on upgrade. On install over an existing same version or upgrade ask to install fresh configuration or preserve existing. On uninstall, ask to remove data and configuration (default to No). Migrate configuration on upgrade #13
• Evaluate possibility of using beat-specific MSI window backgrounds and other graphics assets. Product-specific graphic assets #15
• Evaluate replacing SimpleExec with runner capable of returning exit codes and stdout/stderr (possibly nullean/proc). Process runner replacement #16

References

• Add Windows installer beats#163
• https://github.com/elastic/enhancements/issues/7001

[Mpdreamz]

Support for distinct x86 and x64 msi build workflows.

Are we okay with just x64 installers? x86 only versions of windows are quite rare nowadays.

[ghost]

I suspect it's not a big deal at all, as it's controlled by a single switch. If it turns out to be a problem, We'll restrict to x64 only.

[sophiec20]

I suspect it's not a big deal at all,

It may not be a big deal to flip the switch, but we still have to test, support and maintain x86.

Please only create for x86 if there is a strong need. I do not think this has been established.

[ghost]

I suspect it's not a big deal at all,

It may not be a big deal to flip the switch, but we still have to test, support and maintain x86.
Please only create for x86 if there is a strong need. I do not this has been established.

Hi @sophiec20, I see. Beats team publishes x86 artifacts, so it was reasonable to support them. I'll mention this in our sync-up with them today. In 85c4208, I just pushed, I defaulted bitness to x64.

UPD: I just spoke with @urso. He mentioned that usage of x86 binaries is quite high, so for now they stay as supported variant. x64 will be default for CLI though.

[ghost]

Everything is accounted for in tickets and comments