Add --agent-version flag for flexible Elastic Agent version configuration
#3054
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
teresaromero
commented
Nov 5, 2025
| DataStreamRootPath: dataStreamPath, | ||
| Variant: variantFlag, | ||
| StackVersion: stackVersion.Version(), | ||
| AgentVersion: stackVersion.Version(), |
There was a problem hiding this comment.
The service cmd needs an agent version definition? or the default (same as stack) is used?
There was a problem hiding this comment.
I guess deployers that manage their own agents could use this version, though not sure if we need a different setting for stack and agent version 🤔
In any case this is internal by now, right? No change for users.
⏳ Build in-progress, with failures
Failed CI StepsHistory
|
teresaromero
changed the title
--agent-version flag for flexible Elastic Agent version configuration
teresaromero
commented
Nov 6, 2025
| if url, ok := config.Parameters[stack.ParamServerlessFleetURL]; ok { | ||
| fleetURL = url | ||
| } | ||
| if version, ok := config.Parameters[stack.ParamServerlessLocalStackVersion]; ok { |
There was a problem hiding this comment.
the flag value will be overriden by the config file one
I think it should be the other way around, if a user is setting a flag in the command line, this value should be prioritized over the one in config files.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a new --agent-version flag that allows users to specify a different Elastic Agent version from the stack version when running tests and booting up the stack.
What changed
Added --agent-version flag to stack up, stack update, and test system commands
The flag defaults to the stack version if not specified, maintaining backward compatibility
Environment variables (ELASTIC_AGENT_IMAGE_REF_OVERRIDE) and configuration file settings (stack.image_ref_overrides.elastic-agent) still take precedence over the flag
System tests now support running with different agent versions, making it easier to test compatibility with older agent versions
Why
With the new agent.version condition being introduced in package manifests to specify minimum compatible Elastic Agent versions, we need an easier way to test packages against different agent versions. Previously, you had to use environment variables or modify the config file. Now you can just pass --agent-version 8.10.0 to quickly test with a specific agent version.
This is especially useful for ensuring packages maintain compatibility with older agent versions without breaking changes.
Resolves #2852