[Feature] Allow overriding yaml files used in the apply operation of a test step

[lantingchiang]

Problem Statement

If I have a test like the following:

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
  name: test-basic-resource-creation-succeeds
spec:
  steps:
    - name: basic-pod-creation-should-succeed
      try:
        - apply:
            file: ../resources-always-pass/pods.yaml
        - assert:
            resource:
              apiVersion: v1
              kind: Pod
              metadata:
                name: basic-pod

where pods.yaml contains a pod manifest with metatdata.namespace specified. I would like to remove the namespace field or override it so that it gets created in the ephemeral namespace that chainsaw creates. The reason why I'm not directly removing metadata.namespace from pods.yaml is because the same manifest is used for other things.

Solution Description

There should be options to override fields from yaml files that are referenced in the apply operation. For example, I should be able to specify

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
  name: test-basic-resource-creation-succeeds
spec:
  steps:
    - name: basic-pod-creation-should-succeed
      try:
        - apply:
            file: ../resources-always-pass/pods.yaml
            overrides:
              path: metadata.namespace
              value: ($namespace)
        - assert:
            resource:
              apiVersion: v1
              kind: Pod
              metadata:
                name: basic-pod

to override the key, or

apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
  name: test-basic-resource-creation-succeeds
spec:
  steps:
    - name: basic-pod-creation-should-succeed
      try:
        - apply:
            file: ../resources-always-pass/pods.yaml
            overrides:
              path: metadata.namespace
              value: null
        - assert:
            resource:
              apiVersion: v1
              kind: Pod
              metadata:
                name: basic-pod

to remove the key

Alternatives

No response

Additional Context

No response

Slack discussion

https://kubernetes.slack.com/archives/C067LUFL43U/p1715011398814629

Research

• I have read and followed the documentation AND the troubleshooting guide.
• I have searched other issues in this repository and mine is not recorded.

[welcome]

Thanks for opening your first issue here! Be sure to follow the issue template!

[chipzoller]

Transferred to Chainsaw, not a Kyverno core issue.

[eddycharly]

Thanks for reporting, we could do something specific to override the namespace but a generic solution would be better 🤔