update

Author: vishal-av

docs/continuous-delivery/deploy-srv-diff-platforms/tanzu/tanzu-command-step.md

@@ -2,6 +2,14 @@
 title: Tanzu Command step
 description: Run a CF-enabled shell and use script inputs and outputs
 sidebar_position: 4
+tags:
+  - tanzu-command-step
+  - tanzu-deployments
+  - tanzu-cf-cli
+  - tanzu-harness-expressions
+  - tanzu-script-logging
+  - tanzu-deploy-stage
+
 ---
 
 The Tanzu Command step enables you to run scripts in the same Tanzu environment you are using for deployment in your pipeline.

docs/continuous-delivery/get-started/service-licensing-for-cd.md

@@ -6,6 +6,21 @@ helpdocs_topic_id: ihboxj8xlz
 helpdocs_category_id: Dxej4ug0n5
 helpdocs_is_private: false
 helpdocs_is_published: true
+tags:
+  - cd-services
+  - license-consumption
+  - service-licensing
+  - active-services
+  - service-instances
+  - custom-deployments
+  - pipelines-with-no-service
+  - subscription-page
+  - improved-service-license-tracking
+  - gitops-service-licensing
+  - service-instance-count
+  - licensing-changes
+  - legacy-licenses
+  - license-transition
 ---
 
 Harness Continuous Delivery & GitOps (CD) module uses 'Services' as a key construct in defining and managing the pieces of software that you want to deploy. Since the core value of the CD module is in deploying these services, most Harness customers either directly license by Services (legacy model) or license by Developers (Developer 360 model) and receive services as an included entitlement. More details on the Developer 360 model are available [here](/docs/platform/get-started/subscriptions-licenses/subscriptions).

docs/continuous-delivery/get-started/services-and-environments-overview.md

@@ -8,6 +8,21 @@ helpdocs_is_private: false
 helpdocs_is_published: true
 redirect_from:
   - /docs/continuous-delivery/onboard-cd/cd-concepts/cd-pipeline-basics
+tags:
+  - services
+  - creating-services
+  - creating-environments
+  - service-overrides
+  - override-priority
+  - infrastructure-definitions
+  - infrastructure-tags
+  - values-yaml-overrides
+  - merging-values-yaml
+  - fully-overriding-values
+  - config-files
+  - runtime-inputs-and-expressions
+  - services-and-environments-rbac
+  - environment-groups
 ---
 
 This topic describes Harness Continuous Delivery (CD) services and environments.

docs/continuous-delivery/x-platform-cd-features/services/artifact-sources.md

@@ -2,6 +2,22 @@
 title: CD artifact sources
 description: Connect Harness with the artifact sources to use for deployments.
 sidebar_position: 4
+tags:
+  - artifact-sources
+  - docker
+  - google-container-registry
+  - google-cloud-storage
+  - google-artifact-registry
+  - azure-devops-artifacts
+  - azure-container-registry
+  - amazon-elastic-container-registry
+  - amazon-s3-cloud-storage
+  - amazon-ec2-amis
+  - nexus
+  - artifactory
+  - bamboo
+  - github-packages
+  - custom-artifact-source
 ---
 
 In DevOps, an artifact source is a location where the compiled, tested, and ready-to-deploy software artifacts are stored. These artifacts could be container images, compiled binary files, executables, or any other software components that are part of the application.