From 94e91c54c3fe5e94e2bd28c3e49b2b0d967f484b Mon Sep 17 00:00:00 2001 From: Nageshbansal <76246968+Nageshbansal@users.noreply.github.com> Date: Tue, 12 Mar 2024 17:00:46 +0530 Subject: [PATCH] Update annotation for gitops in event-tracker (#248) Signed-off-by: nagesh bansal --- website/docs/user-guides/gitops-configuration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/docs/user-guides/gitops-configuration.md b/website/docs/user-guides/gitops-configuration.md index 794bae19..911ba0ea 100644 --- a/website/docs/user-guides/gitops-configuration.md +++ b/website/docs/user-guides/gitops-configuration.md @@ -51,7 +51,7 @@ It is also possible to account for the chaos experiments that are created and pu - Once the chaos experiment is pushed to your repository, you’ll notice every chaos experiment has a `experiment_id`. You can get this from the chaos experiment YAML file. You need to copy the id and annotate the target application so that if there’s any change in the application, gitops will sync the chaos experiment using this experiment_id and run it on your target application. You can use the following command: ``` -kubectl annotate deploy/target-application litmuschaos.io/workflow=${experiment_id} +kubectl annotate deploy/target-application litmuschaos.io/experimentId=${experiment_id} ``` ```