From 4a32e57b69bc8ec5c6922e3299668879ff7f57e5 Mon Sep 17 00:00:00 2001 From: Mohammed Janibasha Date: Tue, 5 Nov 2024 13:19:11 +0530 Subject: [PATCH] Update automation-workflow.rst --- workflow-guides/waf/f5-xc-waf-on-k8s/automation-workflow.rst | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/workflow-guides/waf/f5-xc-waf-on-k8s/automation-workflow.rst b/workflow-guides/waf/f5-xc-waf-on-k8s/automation-workflow.rst index 51934ae13..8c6a60461 100644 --- a/workflow-guides/waf/f5-xc-waf-on-k8s/automation-workflow.rst +++ b/workflow-guides/waf/f5-xc-waf-on-k8s/automation-workflow.rst @@ -171,6 +171,10 @@ f5-xc-waf-on-k8s destroy-waf-k8s - http_only = "set to true if want to advertise on http protocol" +Check below image for sample data + +.. image:: /workflow-guides/waf/f5-xc-waf-on-k8s/assets/xc-tfvars.JPG + **STEP 4:** Also update default value of ``aws_waf_ce`` variable in ``variables.tf`` file of ``/aws/eks-cluster``, ``/aws/eks-cluster/ce-deployment`` and ``/shared/booksinfo`` folders if it's not ``infra``. Commit and push your build branch to your forked repo, Build will run and can be monitored in the GitHub Actions tab and TF Cloud console **STEP 5:** Once the pipeline completes, verify your CE, Origin Pool and LB were deployed or destroyed based on your workflow.