Skip to content

[Meta][Feature] Refactor how Elastic Agent know how to run a binary. #222

@ph

Description

@ph

Our spec defines how software is run by the Elastic Agent and what transformation the transpiler needs to execute to convert the configuration from an Agent configuration to a beats configuration. Change are required for the Elastic Agent to understand what is a shipper.

We would like to make the following changes.

  • Allow the Specification to ship with the binaries instead of embedding it.
  • Investigate how Elastic Agent could trust the file.
  • Investigate how Elastic Agent could trust the binary
  • Document the fields in the file.
  • Validate the different fields of the file. (json schema or golang struct)
    • If field is not present we should fails.
  • Allow the file to support multiple entrypoint (process filestream, process tcp)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions