[snehabandla]

Summary

Fixes how a value count's name is resolved (compiler/count.rs resolve_count_binding).

Inside a value count such as count: { value: [...], name: "location", where: ... }, the expression field('location') returned the current loop element instead of the resource's location. The same happened for field conditions whose path equals the count's name, including alias paths and dynamic [if(...)] paths. In Azure Policy a value count's name is only reachable through current(); field() and field conditions always read resource fields. This bug already existed on main.

resolve_count_binding no longer matches field paths against value-count names. Two branches that became unreachable are removed. current() resolution is unchanged.

Testing

• tests/azure_policy/cases/count.yaml has 30 cases, covering:
  • field('location'), alone and alongside current('location');
  • alias field conditions named like the count;
  • a value count inside existenceCondition;
  • names containing [*];
  • the greater: 0 early exit;
  • [if(...)] field paths;
  • value and field counts nested in each other;
  • current() still returning the element.
• Every match case fails before the fix. Each has a twin that the pre-fix code answers differently, except three labelled guards for behaviour this change must keep.
• Two unit tests that asserted the old name matching were replaced.
• All on Rust 1.95.0:
  • cargo fmt --check;
  • clippy with --all-targets --all-features and with --no-default-features;
  • cargo build --all-targets, cargo test --doc, cargo test;
  • the azure_policy lib and integration tests, plus --test aci, --test kata, and OPA with the tests/opa.passing list (2875/0);
  • cargo xtask test-no-std.

Dependencies: none (based on main).

[Copilot]

🟢 Approval recommended

No active review issues are reported for the Azure Policy field-resolution change.

No open issues 🎉

What changed in this PR

Fixes Azure Policy field resolution so value-count names no longer shadow resource fields. Named loop elements remain accessible through current(), while field-count binding behavior is preserved.

Changes:

• Removes value-count name matching from field resolution and related helper branches.
• Updates unit tests and adds 30 regression cases covering name collisions, nested counts, wildcard and dynamic paths, and related-resource evaluation.

File	Description
tests/​azure_policy/​cases/​count.yaml	Adds regression cases and guards for unchanged count behavior.
src/​languages/​azure_policy/​compiler/​count.rs	Restricts field binding resolution to field counts; updates documentation and unit tests.

_{Review effort: Balanced}