Merge branch 'main' into revamp-notification-doc

Author: ashokdevtron

docs/SUMMARY.md

@@ -46,7 +46,7 @@
   * [Catalog Framework](user-guide/global-configurations/catalog-framework.md)
   * [Scoped Variables](user-guide/global-configurations/scoped-variables.md)
   * [Pull Image Digest](user-guide/global-configurations/pull-image-digest.md)
-  * [Tags Policy](user-guide/global-configurations/tags-policy.md)
+  * [Tags](user-guide/global-configurations/tags-policy.md)
   * [Filter Condition](user-guide/global-configurations/filter-condition.md)
   * [Lock Deployment Configuration](user-guide/global-configurations/lock-deployment-config.md)
   * [Image Promotion Policy](user-guide/global-configurations/image-promotion-policy.md)  

docs/user-guide/creating-application/config-approval.md

@@ -1,6 +1,6 @@
 # Protect Configuration
 
-## Introduction
+## Introduction [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
 
 Since resources are created according to the configurations you enter, it's essential to restrict such configurations from direct modifications. For critical environments like production, it becomes necessary to introduce an approval flow for any edits made to the configuration files.
 

docs/user-guide/creating-application/workflow/cd-pipeline.md

@@ -53,7 +53,7 @@ Now, the window will have 3 distinct tabs, and you will see the following additi
 * [Pre-Deployment stage (tab)](#pre-deployment-stage)
 * [Deployment stage (tab)](#deployment-stage)
   * [Pipeline Name (input field)](#pipeline-name)
-  * [Manual approval for deployment (toggle button)](#manual-approval-for-deployment)
+  * [Manual approval for deployment (toggle button)](#manual-approval-for-deployment) [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
   * [Custom Image tag pattern (toggle button)](#custom-image-tag-pattern)
   * [Pull container image with image digest](#pull-container-image-with-image-digest)
 * [Post-Deployment stage (tab)](#post-deployment-stage)

docs/user-guide/creating-application/workflow/ci-pipeline.md

@@ -11,7 +11,7 @@ A CI Workflow can be created in one of the following ways:
 * [Build and Deploy from Source Code](#id-1.-build-and-deploy-from-source-code)
 * [Linked Build Pipeline](#id-2.-linked-build-pipeline)
 * [Deploy Image from External Service](#id-3.-deploy-image-from-external-service)
-* Sync with Environment
+* Sync with Environment [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
 * Create a Job
 
 ![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/creating-application/workflow-ci-pipeline/workflow-ci-1.jpg)
@@ -143,7 +143,7 @@ Select **Create Pipeline**.
 The total timeout for the execution of the CI pipeline is by default set as 3600 seconds. This default timeout is configurable according to the use case (refer [Build Infra](../../global-configurations/build-infra.md)).
 {% endhint %}
 
-##### Scan for Vulnerabilities
+##### Scan for Vulnerabilities 
 
 {% hint style="info" %}
 ### Prerequisite

docs/user-guide/deploying-application/triggering-cd.md

@@ -14,7 +14,7 @@ However, if an image is already deployed, you can identify it by the tag `Active
 
 ![Figure 3: Currently Deployed Image](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/deploying-application/triggering-cd/active-tag.jpg)
 
-## Manual Approval for Deployment
+## Manual Approval for Deployment [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
 
 When [manual approval is enabled](../creating-application/workflow/cd-pipeline.md#4-manual-approval-for-deployment) for the deployment pipeline configured in the workflow, you are expected to request for an image approval before each deployment. Alternatively, you can deploy images that have already been approved once.
 

docs/user-guide/global-configurations/tags-policy.md

@@ -1,4 +1,6 @@
-# Tags Policy
+# Tags
+
+## Introduction [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
 
 Devtron's `Tags Policy` feature enables you to assign tags to your applications. Devtron also offers the option to propagate the tags assigned to an application as labels within the associated Kubernetes resources. 
 

docs/user-guide/security-features.md

@@ -7,8 +7,8 @@ Devtron provides [DevSecOps](https://devtron.ai/product/devsecops) capabilities
 One of the key components of DevSecOps is the detection of security risks. Currently, Devtron supports the following types of scanning:
 
 * Image Scan
-* Code Scan 
-* Kubernetes Manifest Scan
+* Code Scan [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
+* Kubernetes Manifest Scan [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
 
 ![Figure 1: Security Scan Results](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/security-features/security-scan.jpg)
 
@@ -87,7 +87,7 @@ Results of Pre-CD scan will be visible under `Image Scan` and `Kubernetes Manife
 
 ![Figure 8: Pre-CD Scan Results](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/security-features/manifest-scan.gif)
 
-### During Helm App Deployment
+### During Helm App Deployment [![](https://devtron-public-asset.s3.us-east-2.amazonaws.com/images/elements/EnterpriseTag.svg)](https://devtron.ai/pricing)
 
 When you [deploy a helm chart](../user-guide/deploy-chart/deployment-of-charts.md), Devtron will scan the image associated with that helm chart and also the manifests, but unlike Devtron Apps, there is no code scan involved.