From a5ed47515cfbfd0d617613eb81889a025717421c Mon Sep 17 00:00:00 2001 From: RealAnna <89971034+RealAnna@users.noreply.github.com> Date: Wed, 20 Mar 2024 15:29:44 +0100 Subject: [PATCH] docs: replace reference to version with revision in App CRDRef (#3312) Signed-off-by: RealAnna Signed-off-by: RealAnna <89971034+RealAnna@users.noreply.github.com> Co-authored-by: Moritz Wiesinger Signed-off-by: vickysomtee --- docs/docs/reference/crd-reference/app.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/docs/reference/crd-reference/app.md b/docs/docs/reference/crd-reference/app.md index 7e576cacd1c..bbd0f58951c 100644 --- a/docs/docs/reference/crd-reference/app.md +++ b/docs/docs/reference/crd-reference/app.md @@ -117,9 +117,9 @@ The synopsis of the `KeptnApp` resource is changed in the `v1beta1` API version: - If you want to use a `KeptnAppContext` resource with your application, the `name` and `namespace` fields are taken from the annotations of the deployed Kubernetes workloads. The corresponding `KeptnAppContext` resource (if any), must have identical values for these fields. -- The `metadata.version` field is now completely managed by Keptn. +- The `metadata.version` field is now completely managed by Keptn and is computed as the hash of all workloads versions. You do not increment this value to cause a new execution of tasks and evaluations; - the only way to trigger a new execution is to increment the `spec.version` field for the `KeptnApp` resource. + the only way to trigger a new execution is to increment the `spec.revision` field for the `KeptnApp` resource. - The pre/post-deployment tasks and evaluations are now defined in the [KeptnAppContext](appcontext.md) resource rather than in the `KeptnApp` resource.