From 93feffe4ad53ed5919eba22b688bf00284e80174 Mon Sep 17 00:00:00 2001 From: Faeka Ansari Date: Thu, 21 Nov 2024 04:39:46 +0530 Subject: [PATCH] address reviews Co-authored-by: Kent Rancourt --- docs/docs/35-references/10-promotion-steps.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/docs/35-references/10-promotion-steps.md b/docs/docs/35-references/10-promotion-steps.md index 246491d7ca..f0a1f1c1d0 100644 --- a/docs/docs/35-references/10-promotion-steps.md +++ b/docs/docs/35-references/10-promotion-steps.md @@ -987,16 +987,17 @@ branch referenced by the `Application`. This step is commonly the last step in a promotion process. :::note -For Kargo `Stage`s to modify and manage Argo CD `Application` resources, -explicit authorization must be granted in the `Application` manifests. -This is achieved by including the `kargo.akuity.io/authorized-stage` annotation. - -The annotation must be formatted as follows: +For an Argo CD `Application` resource to be managed by a Kargo `Stage`, +the `Application` _must_ have an annotation of the following form: ```yaml kargo.akuity.io/authorized-stage: ":" ``` +Such an annotation offers proof that a user who is themselves authorized +to update the `Application` in question has consented to a specific +`Stage` updating the `Application` as well. + The following example shows how to configure an Argo CD `Application` manifest to authorize the `test` `Stage` of the `kargo-demo` `Project`: