elastic / elastic/package-spec

Add support for different references

Open
#823 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
20
Forks
93
Avg merge
15h 10m
Merged PRs (30d)
12

Description

I would like to have the possibility to add own references in the build.yml for fields that are not in ecs, but standardized across my set of log sources. Those fields will be defined in the same yaml structure, but need to have a different name.

The fact that this needs to be **ecs** seems to be hardcoded at 2 different places.

![Image](https://github.com/user-attachments/assets/9ac02ce8-d05c-489d-9257-afe7118a805d)
![Image](https://github.com/user-attachments/assets/872afe37-bff7-433f-b089-fa73a2cdbc84)
![Image](https://github.com/user-attachments/assets/b1759552-1f01-4264-b36a-86509353842e)

Contributor guide

Open the contributing guide

Research direction

Start by locating the two places where ecs is hardcoded and reviewing how references in build.yml are parsed. Trace the existing ECS-shaped YAML path and determine how an alternate name should be represented. Done means build.yml can declare standardized non-ECS references with a different name while preserving existing ECS references.

Written by the indexing model from the issue text.

Assessment

Tech stack
yaml
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.