feat(fleet): add support for duration variable type#231027
Merged
andrewkroh merged 6 commits intoelastic:mainfrom Sep 5, 2025
Merged
feat(fleet): add support for duration variable type#231027andrewkroh merged 6 commits intoelastic:mainfrom
andrewkroh merged 6 commits intoelastic:mainfrom
Conversation
Contributor
|
Pinging @elastic/fleet (Team:Fleet) |
2 tasks
1af15b9 to
fdd7aed
Compare
Add support for a new RegistryVarType named 'duration' with validation logic. The implementation includes: - Add 'duration' to RegistryVarType enum - Add 'min_duration' and 'max_duration' to RegistryVarsEntryKeys - Implement duration parsing and validation logic - Add validation for min/max duration constraints - Add unit tests Relates elastic/package-spec#948
fdd7aed to
c18bf1f
Compare
Contributor
💛 Build succeeded, but was flaky
Failed CI StepsMetrics [docs]Public APIs missing comments
Page load bundle
History
|
shahargl
pushed a commit
to shahargl/kibana
that referenced
this pull request
Sep 7, 2025
This commit introduces support for a `duration` variable type in Fleet package policies, aligning with the package-spec v3.5.0. This change adds `min_duration` and `max_duration` constraints, allowing packages to define acceptable ranges for duration values. This provides immediate validation and feedback for users in the UI and API, preventing invalid or out-of-range duration inputs. Relates elastic/package-spec#948
KodeRad
pushed a commit
to KodeRad/kibana
that referenced
this pull request
Sep 15, 2025
This commit introduces support for a `duration` variable type in Fleet package policies, aligning with the package-spec v3.5.0. This change adds `min_duration` and `max_duration` constraints, allowing packages to define acceptable ranges for duration values. This provides immediate validation and feedback for users in the UI and API, preventing invalid or out-of-range duration inputs. Relates elastic/package-spec#948
CAWilson94
pushed a commit
to CAWilson94/kibana
that referenced
this pull request
Sep 24, 2025
This commit introduces support for a `duration` variable type in Fleet package policies, aligning with the package-spec v3.5.0. This change adds `min_duration` and `max_duration` constraints, allowing packages to define acceptable ranges for duration values. This provides immediate validation and feedback for users in the UI and API, preventing invalid or out-of-range duration inputs. Relates elastic/package-spec#948
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
This commit introduces support for a
durationvariable type in Fleet packagepolicies, aligning with the package-spec v3.5.0.
This change adds
min_durationandmax_durationconstraints, allowingpackages to define acceptable ranges for duration values. This provides
immediate validation and feedback for users in the UI and API, preventing
invalid or out-of-range duration inputs.
Relates elastic/package-spec#948
Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
release_note:breakinglabel should be applied in these situations.release_note:*label is applied per the guidelinesbackport:*labels.Screenshots
Release note
Adds support for a new duration variable type in Fleet packages which provides better input validation of duration strings (e.g. 1h30m) in configurations.