Ability to parse string expressions #25
Merged
Conversation
This file contains 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
jordipiqueselles
force-pushed
the
jordi/expr-parser
branch
from
576a9df
to
33210c9
Compare
jordipiqueselles
added
enhancement
jordipiqueselles
force-pushed
the
jordi/expr-parser
branch
from
33210c9
to
736d0f3
Compare
jordipiqueselles
added
enhancement
When we define the conditions for a webhook, now we can use plain string expressions like `.containers.0.maxCPUs >= .containers.0.minCPUs + 2`. This feature will be available in the next schema version, so the behaviour of the "alpha1v1" schema keeps being the same.
jordipiqueselles
force-pushed
the
jordi/expr-parser
branch
from
736d0f3
to
3d69518
Compare
jordipiqueselles
added
enhancement
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.
When we define the conditions for a webhook, now we can use plain string expressions like
.containers.0.maxCPUs >= .containers.0.minCPUs + 2.This feature will be available in the next schema version, so the behaviour of the "alpha1v1" schema keeps being the same.