Aleksei Sviridkin 4e3a679e7b test(apps): anchor index-addressed negative asserts to what they name ...

notContains passes whenever its path resolves to something that
simply lacks the forbidden content, and a different element at the
same index qualifies. These guards would go green if the Role's rule
order changed or a nodePool were added ahead of the one they name,
while the resource they forbid came back on the element they meant.

Assert the addressed element before asserting what it must not have.
The Kafka Role rules have no identifier, so the anchor is the
in-cluster bootstrap Service that rule must keep. The OpenSearch pool
does have one, `component`, and that is what is pinned: roles are
shared between pools, so a role-based anchor would be satisfied by a
second data-bearing pool inserted ahead of this one.

Each anchor was checked against the shift it exists to catch, and
against the same shift with the anchors removed: without them the
blocks stay green while the forbidden content is back on the element
they name.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <f@lex.la>

2026-08-07 15:35:43 +03:00

..

opensearch_test.yaml

test(apps): anchor index-addressed negative asserts to what they name

2026-08-07 15:35:43 +03:00

resourcepreset_test.yaml

test(apps): backward-compat helm-unittest and CI invariants

2026-05-11 21:09:50 +03:00

security_test.yaml

[apps] Add managed OpenSearch service

2026-02-16 22:54:41 +01:00

users_test.yaml

[apps] Add managed OpenSearch service

2026-02-16 22:54:41 +01:00