Codecov Report

❌ Patch coverage is 97.56098% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 67.70%. Comparing base (de0a923) to head (c3be2f6).
⚠️ Report is 1 commits behind head on main.

@@            Coverage Diff             @@
##             main    #2654      +/-   ##
==========================================
+ Coverage   67.08%   67.70%   +0.62%     
==========================================
  Files         149      149              
  Lines        5723     5757      +34     
==========================================
+ Hits         3839     3898      +59     
+ Misses       1624     1599      -25     
  Partials      260      260              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@eddycharly is test coverage ok like this?
the current missing covered lines do not have any tests yet.

I have an alternative approach here:
#2699

This approach works with an annotation instated of an attribute in Patch action struct.
Resources that need a subresource patch would add the annotation chainsaw.kyverno.io/patch-subresource where the value is the name of the subresource to be patched.

This allows only using one patch action fit a file that contain resources with normal patches as well as suresoruce patches.

@eddycharly what would you prefer?

Sample:

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
  name: basic-deployment
spec:
  steps:
    - name: deploy-application
        - description: Simulate Readiness of provider resources
          patch:
            file: 02-patch-provider-resources.yaml

with the patch file: 02-patch-provider-resources.yaml

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: basic-deployment-dev-app
  namespace: basic-deployment-dev
status:
  sync:
    status: OutOfSync
---
apiVersion: identity.vault.m.upbound.io/v1alpha1
kind: GroupAlias
metadata:
  name: basic-deployment-owner
  namespace: crossplane-resources
  annotations:
    chainsaw.kyverno.io/patch-subresource: status
status:
  conditions:
    - type: Ready
      status: "True"
      reason: ManuallySet
      message: Patched via chainsaw
      lastTransitionTime: "2026-03-28T10:51:35Z"