In a past post: http://sferich888.blogspot.com/2017/01/learning-using-jsonpath-with-openshift.html
I discussed what json path could do. Today I learned that filters (are only capable of doing simple comparisons (==, !=, <=, >=) type operations.
The tl;dr version is (see regex):
https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/util/jsonpath/parser.go#L338
However because Kubernetes (and by proxy OpenShift) use the jsonpath extension from exponent-io and the golang re2 (regex engine).
The above "filter" operation to find and compare parts of the path are only (as of right now) capable of simple operations.
As a technology enthusiast, software developer and all around geek. These are my feeble attempts to log my personal experiments and projects, contained with in is the knowledge obtained during there trials.
Subscribe to:
Post Comments (Atom)
Its the little things (like opening a web browser)
Sometimes as your developing a solution/script for a problem your faced with interesting challenges where the dumbest workaround (opening a ...
-
As part of an effort to automate what I do with OpenShift, I had to learn how to take advantage of OpenShift's "watch" QueryPa...
-
Sometimes as your developing a solution/script for a problem your faced with interesting challenges where the dumbest workaround (opening a ...
-
For a few days, not I have needed a dynamic way to create DNS entries, or Host on my DNS/IDM provider. So I set out on a quest to see if I...
No comments:
Post a Comment