"<" operator in jq filter fails the build about content HOT 4 OPEN

Hi, could you tell us how have you tried to escape the < sign? Have you tried the xml way? <

Regardless, there is another approach that you can take

Instead of using the jqfilter to check that the inequality deschedulingIntervalSeconds < 3600 is true.
You can do the comparison in the template:

I have not tested, but the following may work:

{{% set jqfilter = '[.spec.deschedulingIntervalSeconds]' %}}

template:
  name: yamlfile_value
  vars:
    ocp_data: "true"
    filepath: {{{ openshift_filtered_path('/apis/operator.openshift.io/v1/namespaces/openshift-kube-descheduler-operator/kubedeschedulers/cluster', jqfilter) }}}
    yamlpath: "[:]"
    check_existence: "all_exist"
    entity_check: "all"
    values:
      - value: 3600
        type: "int"
        operation: "less than"

For more info about the template's capability, check https://complianceascode.readthedocs.io/en/latest/templates/template_reference.html#yamlfile-value

from content.

I think I tried these options "<" '<' and \<

Thanks for the suggestion. The problem is that I am also checking for another key and only if both statements are true the check is compliant. This is my full jqfilter:
{{% set jqfilter = '[if (any(.spec.profiles[]; . =="LifecycleAndUtilization")) == true and ((.spec.deschedulingIntervalSeconds <= {{.kube_descheduler_interval}}) == true) then true else false end]' %}}

from content.

@ermeratos You might want to separate the two checks into their own rules; or,
if one of the checks can be considered an applicability condition for the other check, it could be made into a platform check. When the applicability check is false, the rule results is not applicable, instead of PASS/FAIL.
I'm just not sure how well the applicability check will work with jqfilters.

Did the xml escaping suggestion work for you?

from content.

I wanted to prevent the two checks from being separated. Thank you for the tip about the platform check, I might try that out.

I completely missed your info about the XML escape, otherwise I could have tested it earlier. Because it actually works with <. Even <= seems to be working.

from content.