elastic / elastic/elastic-agent

[proposal] modify updating beats and otel dependencies

Open
#13,191 4 comments 1 reaction 0 assignees View on GitHub
discuss Team:Elastic-Agent
Dominant language
Go
Stars
275
Forks
264
Avg merge
1d 23h
Merged PRs (30d)
312

Description

Currently we have a GitHub action to update beats and a GitHub action to update otel dependencies.

This can create the scenario where the version of otel in beats submodule and elastic-agent is different, which may cause problems.

I propose that we update the otel dependencies in beats first, and then have one GitHub action in the elastic-agent repository that updates the beats submodule, and if the beats submodule imports a newer version of otel dependencies update those to match.

Now that I have proposed a solution, I expect [Cunningham's Law](https://meta.wikimedia.org/wiki/Cunningham%27s_Law) will quickly be applied.

Contributor guide

Open the contributing guide

Research direction

Start by reading the existing GitHub Actions that update the beats submodule and OpenTelemetry dependencies. Trace how each workflow currently selects versions, then verify the proposed single workflow keeps the beats and otel dependencies aligned after an update.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions, go
Domain
ci-cd, devops
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.