Unexpected reports when using nested blocks
Some specific cases of nested block are breaking the compliance computation.
I was using some complex nested block logic to organize one of my technique, and ended up with a lot (~85%) of unexpected reports. The strange thing here is that the reports seems correct,
they were the same due to the nature of the reporting, but where all marked as unexpected whenever I had more than 4 of them similar.
- A parent block
- at least 4 children blocks with the same method, with the same component key (resource parameter in rudder language).
I was working from a rudderlang source, generating a json and importing it via the API. It seems like if I export the technique after having it imported this way, then import the newly exported json, the technique is correct and does not generate any unexpected reports anymore.
To import the rd file, I used the following steps:
/opt/rudder/bin/rudderc technique read -i "technique.rd" curl --silent -k --header "X-API-Token: $(cat /var/rudder/run/api-token)" --header "Content-type: application/json" --request PUT https://localhost/rudder/api/latest/techniques --data "@technique.json"