Add conditions.agent.version into integration and input manifest spec with validation
#999
+4,836
−1
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
|
test-integrations |
|
Created or updated PR in integrations repository to test this version. Check elastic/integrations#15665 |
jsoriano
reviewed
Oct 16, 2025
jsoriano
reviewed
Oct 16, 2025
- Refactor error handling in ValidateMinimumAgentVersion to check for valid semver constraints. - Adjust test cases to reflect changes in agent.version validation logic. - Modify integration manifest specifications to require agent.version as a constraint. - Update example manifests to use new versioning format.
… elastic and kibana to content packages
teresaromero
commented
Oct 17, 2025
teresaromero
commented
Oct 17, 2025
teresaromero
commented
Oct 17, 2025
teresaromero
commented
Oct 17, 2025
teresaromero
changed the title
conditions.agent.version into integration manifest spec with validationconditions.agent.version into integration and input manifest spec with validation
jsoriano
reviewed
Oct 17, 2025
…tegration packages
jsoriano
previously approved these changes
Oct 23, 2025
jsoriano
previously approved these changes
Oct 23, 2025
mrodm
previously approved these changes
Oct 23, 2025
…nt condition in manifest
mrodm
previously approved these changes
Oct 23, 2025
💚 Build Succeeded
History
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
What does this PR do?
Adds a new property into the integration and input spec to add the minimum agent version a package is compatible with.
The new field is required after 3.6
Why is it important?
The Elastic Agent running at Kibana, might not be compatible with the integration. This helps Fleet read the agent version an integration is compatible with and is able to warn the user if is not compatible.
Checklist
Added unit tests
Updated test packages for 3.6 version to include the now required field
I have added test packages to
test/packagesthat prove my change is effective.I have added an entry in
spec/changelog.yml.Related issues
Resolves #970