Update¶
The update
operation lets you define resources that should be updated in the Kubernetes cluster during the test step. These can be configurations, deployments, services, or any other Kubernetes resource.
Configuration¶
Reference documentation
Warning
If the resource to be updated doesn't exist in the cluster, the step will fail.
Usage examples¶
Below is an example of using update
in a Test
resource.
Using a specific file
apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
name: example
spec:
steps:
- try:
# ...
- update:
file: my-configmap.yaml
# ...
Using file path expressions
apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
name: example-multi
spec:
steps:
- try:
# ...
- update:
file: "configs/*.yaml"
# ...
Using an URL
apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
name: example
spec:
steps:
- try:
# ...
- update:
file: https://raw.githubusercontent.com/kyverno/chainsaw/main/testdata/resource/valid.yaml
# ...
Using an inline resource
apiVersion: chainsaw.kyverno.io/v1alpha1
kind: Test
metadata:
name: example
spec:
steps:
- try:
# ...
- update:
resource:
apiVersion: v1
kind: ConfigMap
metadata:
name: chainsaw-quick-start
data:
foo: bar
# ...
Operation check¶
Below is an example of using an operation check.
With check
# ...
- update:
file: my-configmap.yaml
expect:
- match:
# this check applies only if the match
# statement below evaluates to `true`
apiVersion: v1
kind: ConfigMap
check:
# an error is expected, this will:
# - succeed if the operation failed
# - fail if the operation succeeded
($error != null): true
# ...
With check
# ...
- update:
resource:
apiVersion: v1
kind: ConfigMap
metadata:
name: chainsaw-quick-start
data:
foo: bar
expect:
- match:
# this check applies only if the match
# statement below evaluates to `true`
apiVersion: v1
kind: ConfigMap
check:
# an error is expected, this will:
# - succeed if the operation failed
# - fail if the operation succeeded
($error != null): true
# ...