We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using the matchFields selector with the DoesNotExist operator, the option does not match when the json path does not exist.
DoesNotExist
Please provide a set of steps to reproduce the behavior (example):
first
second
apiVersion: carto.run/v1alpha1 kind: ClusterSupplyChain metadata: name: test selector: test: true resources: - name: first templateRef: kind: ClusterTemplate options: - name: first selector: matchFields: - key: .spec.params[?(@.name=="non-existent")] operator: DoesNotExist - name: second selector: matchFields: - key: .spec.params[?(@.name=="non-existent")] operator: Exists
apiVersion: carto.run/v1alpha1 kind: Workload metadata: name: test labels: test: true spec: params: - name: some-param value: true
The first template should match.
The status reports an error that 0 templates matched.
The text was updated successfully, but these errors were encountered:
martyspiewak
Successfully merging a pull request may close this issue.
Bug description:
When using the matchFields selector with the
DoesNotExist
operator, the option does not match when the json path does not exist.Steps to reproduce:
Please provide a set of steps to reproduce the behavior (example):
first
andsecond
):Expected behavior:
The first template should match.
Actual behavior:
The status reports an error that 0 templates matched.
The text was updated successfully, but these errors were encountered: