> For the complete documentation index, see [llms.txt](https://developer.harness.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.harness.io/continuous-delivery/troubleshooting-and-resources/tutorials/google-cloud-deployments/gcp-cloud-func.md). # Google Cloud Functions serverless deployments This tutorial will get you started with Harness Continuous Delivery (CD). We will guide you through deploying new Google Cloud Functions to Google Cloud using a Harness CD pipeline. {% hint style="info" %} [Sign up today to unleash the potential of intelligent Harness CD](https://app.harness.io/auth/#/signup/?module=cd\&utm_source=website\&utm_medium=harness-developer-hub\&utm_campaign=cd-plg\&utm_content=tutorials-cd-serverless-gcp-function). {% endhint %} Harness CD pipelines help you to orchestrate and automate your Google Cloud Function deployments and push updated functions to Google Cloud. Pipelines allow extensive control over how you want to progress functions through various dev/test/stage/prod environments while running a variety of scans and tests to ensure your quality and stability standards. ### Before you begin Verify that you have the following: 1. **Obtain GitHub personal access token with the repo scope**. See the GitHub documentation on [creating a personal access token](https://help.github.com/en/github/authenticating-to-github/creating-a-personal-access-token-for-the-command-line). 2. **A Kubernetes cluster**. Use your own Kubernetes cluster or we recommend using [K3D](https://k3d.io/v5.5.1/) for installing a Harness Delegate. * Check [Delegate system requirements](/harness-ai/use-harness-platform/delegates/delegate/delegate-concepts/delegate-requirements.md). 3. **Install the** [**Docker**](https://helm.sh/docs/intro/install/) in order to install the Docker delegate. 4. **Fork the** [**harnesscd-example-apps**](https://github.com/harness-community/harnesscd-example-apps/fork) repository through the GitHub website. * For details on Forking a GitHub repository, go to [GitHub docs](https://docs.github.com/en/get-started/quickstart/fork-a-repo#forking-a-repository) for more information on forking a GitHub repository. 5. \*\* Google Cloud Function and Google Cloud Storage permissions\*\*. Harness supports Google Cloud Functions **1st gen** and **2nd gen**. There are minor differences in the permissions required by each generation. For a detailed breakdown, go to [Access control with IAM from Google](https://cloud.google.com/functions/docs/concepts/iam). ### Google Cloud Function Support Cloud Functions offers two product versions: Cloud Functions **1st gen**, the original version, and Cloud Functions **2nd gen**, a new version built on Cloud Run and Eventarc to provide an enhanced feature set. Harness supports deploying Google Functions 1st gen and 2nd gen. To get more information on Google Functions 1st gen and 2nd gen, go to [Cloud Functions version comparison](https://cloud.google.com/functions/docs/concepts/version-comparison). We suggest opting for Cloud Functions **2nd gen** whenever feasible for new functions, as it offers a range of additional features. For more information, go to [New in Cloud Functions(2nd Gen)](https://cloud.google.com/functions/docs/concepts/version-comparison#new-in-2nd-gen). ### Cloud Functions Limitations * For Google Cloud Functions 2nd gen, Harness does not support [Google Cloud Source Repository](https://cloud.google.com/functions/docs/deploy#from-source-repo) at this time. Only Google Cloud Storage is supported. * For Google Cloud Functions 1st gen, Harness supports both Google Cloud Storage and Google Cloud Source. ### Steps to perform on Google Cloud * Make sure your Google Cloud account credentials have the required permissions for **Google Cloud Function** and **Google Cloud Storage**, as mentioned above. * Download the **hello\_world.zip** for 1st gen and **helloHttp.zip** for 2nd gen files from [GitHub](https://github.com/harness-community/harnesscd-example-apps/tree/master/google_cloud_function). * Log into the Google Cloud console and create a Google Cloud Storage bucket. For details, go to [Create a new bucket](https://cloud.google.com/storage/docs/creating-buckets). * Once the bucket is created, select **UPLOAD FILES** and upload the file **hello\_world.zip** for 1st gen or **helloHttp.zip** for 2nd gen. ### Getting Started with Harness CD 1. Log into [Harness](https://app.harness.io/). 2. Select **Projects**, and then select **Default Project**. {% hint style="warning" %} For the pipeline to run successfully, please follow the remaining steps as they are, including the naming conventions. {% endhint %} #### Delegate
What is the Harness Delegate? The Harness Delegate is a service that runs in your local network or VPC to establish connections between the Harness Manager and various providers such as artifacts registries, cloud platforms, etc. The delegate is installed in the target infrastructure, for example, a Kubernetes cluster, and performs operations including deployment and integration. Learn more about the delegate in the [Delegate Overview](/harness-ai/use-harness-platform/delegates/delegate/delegate-concepts/delegate-overview.md).
1. Under **Project Setup**, select **Delegates**. * Select **Delegates**. * Select **New Delegate**. * Select **Docker**. For this tutorial, let's explore how to install a delegate using Docker. * In the command provided, `ACCOUNT_ID` and `MANAGER_ENDPOINT` are auto-populated values that you can obtain from the delegate installation wizard. * Replace **DELEGATE\_TOKEN** in the command with the token from the wizard. ```bash docker run -dit --cpus=1 --memory=2g \ -e DELEGATE_NAME=docker-delegate \ -e NEXT_GEN="true" \ -e DELEGATE_TYPE="DOCKER" \ -e ACCOUNT_ID=ACCOUNT_ID \ -e DELEGATE_TOKEN=DELEGATE_TOKEN \ -e MANAGER_HOST_AND_PORT=https://app.harness.io/gratis harness/delegate:23.05.79310 ``` * Select **Verify** to verify that the delegate is installed successfully and can connect to the Harness Manager. {% hint style="info" %} You can also follow the [Install Harness Delegate on Kubernetes or Docker](/harness-ai/troubleshooting-and-resources/tutorials/install-delegate.md) steps to install the delegate using the Harness Terraform Provider or a Kubernetes manifest. {% endhint %} #### Secrets
What are Harness secrets? Harness offers built-in secret management for encrypted storage of sensitive information. Secrets are decrypted when needed, and only the private network-connected Harness Delegate has access to the key management system. You can also integrate your own secret manager. To learn more about secrets in Harness, go to [Harness Secret Manager Overview](/harness-ai/use-harness-platform/secrets/secrets-management/harness-secret-manager-overview.md).
1. Under **Project Setup**, select **Secrets**. * Select **New Secret**, and then select **Text**. * Enter the secret name `harness_gitpat`. * For the secret value, paste the GitHub personal access token you saved earlier. * Select **Save**. 2. Under **Project Setup**, select **Secrets**. * Select **New Secret**, and then select **File**. * Enter the secret name `gcpsecret`. * For the secret value, upload the Google Cloud's account service key file for your service account, which you can download from your [GCP project](https://developers.google.com/workspace/guides/create-credentials#create_credentials_for_a_service_account). * Select **Save**. {% tabs %} {% tab title="2nd Gen" %} {% tabs %} {% tab title="UI" %} #### Connectors
What are connectors? Connectors in Harness enable integration with 3rd party tools, providing authentication and operations during pipeline runtime. For instance, a GitHub connector facilitates authentication and fetching files from a GitHub repository within pipeline stages. For more details, go to [Connectors](/harness-ai/use-harness-platform/connectors.md).
1. Create the **GitHub connector**. * Copy the contents of [github-connector.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/github-connector.yml). * In your Harness project in the Harness Manager, under **Project Setup**, select **Connectors**. * Select **Create via YAML Builder** and paste the copied YAML. * Assuming you have already forked the [harnesscd-example-apps](https://github.com/harness-community/harnesscd-example-apps/fork) repository mentioned earlier, replace `GITHUB_USERNAME` with your GitHub account username in the YAML. * In `projectIdentifier`, verify that the project identifier is correct. You can see the Id in the browser URL (after `account`). If it is incorrect, the Harness YAML editor will suggest the correct Id. * Select **Save Changes** and verify that the new connector named **harness\_gitconnector** is successfully created. * Finally, select **Connection Test** under **Connectivity Status** to ensure the connection is successful. 2. Create the **GCP connector**. * Copy the contents of [gcp-connector.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/gcp-connector.yml). * In your Harness project, under **Project Setup**, select **Connectors**. * Select **Create via YAML Builder** and paste the copied YAML. * Select **Save Changes** and verify that the new connector named **gcpconnector** is successfully created. * Finally, select **Connection Test** under **Connectivity Status** to verify the connection is successful. #### Environment
What are Harness environments? Environments define the deployment location, categorized as **Production** or **Pre-Production**. Each environment includes infrastructure definitions for serverless functions, VMs, Kubernetes clusters, or other target infrastructures. To learn more about environments, go to [Environments overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/environments/environment-overview.md).
1. In your Harness project, select **Environments**. * Select **New Environment**, and then select **YAML**. * Copy the contents of [environment.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/environment.yml), paste it into the YAML editor, and select **Save**. * In your new environment, select the **Infrastructure Definitions** tab. * Select **Infrastructure Definition**, and then select **YAML**. * Copy the contents of [infrastructure-definition.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/infrastructure-definition.yml) and paste it into the YAML editor. * Replace `CLOUD PROJECT NAME` with your GCP project name. * Replace `REGION` with your GCP region name. * Select **Save** and verify that the environment and infrastructure definition are created successfully. #### Services
What are Harness services? In Harness, services represent what you deploy to environments. You use services to configure variables, manifests, functions, and artifacts. The **Services** dashboard provides service statistics like deployment frequency and failure rate. To learn more about services, go to [Services overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/services-overview.md).
1. In your Harness project, select **Services**. * Select **New Service**. * Enter the name `hello_http`. * Select **Save**, and then **YAML** (on the **Configuration** tab). * Select **Edit YAML**, copy the contents of [service.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/2nd_gen/service.yml), and paste the into the YAML editor. * Replace `CLOUD PROJECT NAME` with your GCP project name. * Replace `CLOUD BUCKET NAME` with your GCP bucket name. * Select **Save**, and verify that the service **hello\_http** is successfully created. #### Pipeline
What are Harness pipelines? A pipeline is a comprehensive process encompassing integration, delivery, operations, testing, deployment, and monitoring. It can utilize CI for code building and testing, followed by CD for artifact/function deployment in production. A CD Pipeline is a series of stages where each stage deploys a service to an environment. To learn more about CD pipeline basics, go to [CD pipeline basics](/continuous-delivery/new-to-continuous-delivery/overview.md#pipeline).
1. In your Harness project, select **Pipelines**. * Select **Create a Pipeline**. * Enter the name `hello_http`. * Select **Inline** to store the pipeline in Harness. * Select **Start**. * In **Pipeline Studio**, select **YAML**. * Select **Edit YAML** and choose any of the following execution strategies. Paste the respective YAML based on your selection. {% tabs %} {% tab title="Canary" %}
What are Canary deployments? A canary deployment updates nodes/functions/etc. in a single environment gradually, allowing you to use gates between increments and shift traffic as needed. Canary deployments allow incremental updates and ensure a controlled rollout process. For more information, go to [When to use Canary deployments](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-concepts.md#when-to-use-canary-deployments).
1. Copy the contents of [canary-pipeline.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/2nd_gen/canary-pipeline.yml). 2. In your Harness pipeline YAML editor, paste the YAML. 3. Select **Save**. You can switch to the **Visual** editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% tab title="Blue Green" %}
What are Blue Green deployments? Blue Green deployments involve running two identical environments (stage and prod) simultaneously with different service versions. QA and UAT are performed on a **new** service version in the stage environment first. Next, traffic is shifted from the prod environment to stage, and the previous service/function version running on prod is scaled down. Blue Green deployments are also referred to as red/black deployment by some vendors. For more information, go to [When to use Blue Green deployments](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-concepts.md#when-to-use-blue-green-deployments).
1. Copy the contents of [bluegreen-pipeline.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/2nd_gen/bluegreen-pipeline.yml). 2. In your Harness pipeline YAML editor, paste the YAML. 3. Select **Save**. You can switch to the **Visual** pipeline editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% tab title="Basic" %}
What are Basic deployments? For Google Cloud Functions, the basic deployment execution strategy deploys the new function version and routes 100% of traffic from the old version to the new function version.
1. Copy the contents of [basic-pipeline.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/2nd_gen/basic-pipeline.yml). 2. In your Harness pipeline YAML editor, paste the YAML. 3. Select **Save**. You can switch to the **Visual** pipeline editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% endtabs %} {% endtab %} {% tab title="CLI" %} 1. Download and configure the Harness CLI. {% tabs %} {% tab title="MacOS" %} ```bash curl -LO https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-darwin-amd64.tar.gz tar -xvf harness-v0.0.25-Preview-darwin-amd64.tar.gz export PATH="$(pwd):$PATH" echo 'export PATH="'$(pwd)':$PATH"' >> ~/.bash_profile source ~/.bash_profile harness --version ``` {% endtab %} {% tab title="Linux" %} {% tabs %} {% tab title="ARM" %} ```bash curl -LO https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-linux-arm64.tar.gz tar -xvf harness-v0.0.25-Preview-linux-arm64.tar.gz ``` {% endtab %} {% tab title="AMD" %} ```bash curl -LO https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-linux-amd64.tar.gz tar -xvf harness-v0.0.25-Preview-linux-amd64.tar.gz ``` {% endtab %} {% endtabs %} {% endtab %} {% tab title="Windows" %} ``` a. Open Windows Powershell and run the command below to download the Harness CLI. ``` ``` Invoke-WebRequest -Uri https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-windows-amd64.zip -OutFile ./harness.zip ``` ```` b. Extract the downloaded zip file and change the directory to extracted file location. c. Follow the steps below to make it accessible via terminal. ``` $currentPath = Get-Location [Environment]::SetEnvironmentVariable("PATH", "$env:PATH;$currentPath", [EnvironmentVariableTarget]::Machine) ``` d. Restart terminal. ```` {% endtab %} {% endtabs %} 2. Clone the Forked **harnesscd-example-apps** repo and change directory. ```bash git clone https://github.com/GITHUB_ACCOUNTNAME/harnesscd-example-apps.git cd harnesscd-example-apps ```

Replace GITHUB_ACCOUNTNAME with your GitHub account name.

3. Log into Harness from the CLI. ```bash harness login --api-key --account-id HARNESS_API_TOKEN ```

Replace HARNESS_API_TOKEN with Harness API token that you obtained during the prerequisite section of this tutorial.

What are connectors? Connectors in Harness enable integration with 3rd party tools, providing authentication and operations during pipeline runtime. For instance, a GitHub connector facilitates authentication and fetching files from a GitHub repository within pipeline stages. For more details, go to [Connectors](/harness-ai/use-harness-platform/connectors.md).
1. Create the **GitHub connector**. 1. In `projectIdentifier`, verify that the project identifier is correct. You can see the Id in the browser URL (after `account`). If it is incorrect, the Harness YAML editor will suggest the correct Id. 2. Now create the **GitHub connector** using the following CLI command: ``` harness connector --file "/google_cloud_function/github-connector.yml" apply ``` 2. Create the **GCP connector**. 1. In `projectIdentifier`, verify that the project identifier is correct. You can see the Id in the browser URL (after `account`). If it is incorrect, the Harness YAML editor will suggest the correct Id. 2. Now create the **AWS Connector** using the following CLI command: ``` harness connector --file "/google_cloud_function/gcp-connector.yml" apply ``` #### Environment
What are Harness environments? Environments define the deployment location, categorized as **Production** or **Pre-Production**. Each environment includes infrastructure definitions for serverless functions, VMs, Kubernetes clusters, or other target infrastructures. To learn more about environments, go to [Environments overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/environments/environment-overview.md).
1. Use the following CLI command to create **Environments** in your Harness project: ``` harness environment --file "/google_cloud_function/environment.yml" apply ``` 2. In your new environment, add an **Infrastructure Definitions** using the following CLI command: ``` harness infrastructure --file "/google_cloud_function/infrastructure-definition.yml" apply ``` #### Services
What are Harness services? In Harness, services represent what you deploy to environments. You use services to configure variables, manifests, functions, and artifacts. The **Services** dashboard provides service statistics like deployment frequency and failure rate. To learn more about services, go to [Services overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/services-overview.md).
1. Use the following CLI command to create **Services** in your Harness project. ``` harness service -file "/google_cloud_function/2nd_gen/service.yml" apply ``` #### Pipeline
What are Harness pipelines? A pipeline is a comprehensive process encompassing integration, delivery, operations, testing, deployment, and monitoring. It can utilize CI for code building and testing, followed by CD for artifact/function deployment in production. A CD Pipeline is a series of stages where each stage deploys a service to an environment. To learn more about CD pipeline basics, go to [CD pipeline basics](/continuous-delivery/new-to-continuous-delivery/overview.md#pipeline).
{% tabs %} {% tab title="Canary" %}
What are Canary deployments? A canary deployment updates nodes in a single environment gradually, allowing you to use gates between increments. Canary deployments allow incremental updates and ensure a controlled rollout process. For more information, go to [When to use Canary deployments](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-concepts.md#when-to-use-canary-deployments).
1. Enter this CLI command to create a canary deployment using the example YAML file: ``` harness pipeline --file "/google_cloud_function/2nd_gen/canary-pipeline.yml" apply ``` 2. In Harness, you can switch to the **Visual** editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% tab title="Blue Green" %}
What are Blue Green deployments? Blue Green deployments involve running two identical environments (stage and prod) simultaneously with different service versions. QA and UAT are performed on a **new** service version in the stage environment first. Next, traffic is shifted from the prod environment to stage, and the previous service/function version running on prod is scaled down. Blue Green deployments are also referred to as red/black deployment by some vendors. For more information, go to [When to use Blue Green deployments](/continuous-delivery/use-continuous-delivery/manage-deployments/deployment-concepts.md#when-to-use-blue-green-deployments).
1. Enter this CLI command to create a blue green deployment using the example YAML file: ``` harness pipeline --file "/google_cloud_function/2nd_gen/bluegreen-pipeline.yml" apply ``` 2. You can switch to the **Visual** pipeline editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% tab title="Basic" %}
What are Basic deployments? For Google Cloud Functions, the basic deployment execution strategy deploys the new function version and routes 100% of traffic from the old version to the new function version.
1. Enter this CLI command to create a basic deployment using the example YAML file: ``` harness pipeline --file "/google_cloud_function/2nd_gen/basic-pipeline.yml" apply ``` 2. You can switch to the **Visual** pipeline editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% endtabs %} {% endtab %} {% endtabs %} Finally, it's time to execute your pipeline. 1. Select **Run**, and then select **Run Pipeline** to initiate the deployment. * Observe the execution logs as Harness deploys the function. * After a successful execution, you can check the deployment on your Google Cloud Function console. #### Congratulations!🎉 You've just learned how to use Harness CD to deploy a Google Cloud Function to Google Cloud. Keep learning about Harness CD. For example, add [Triggers](/harness-ai/use-harness-platform/triggers/triggering-pipelines.md) to your pipeline that initiate pipeline deployments in response to Git events. {% endtab %} {% tab title="1st Gen" %} ### Getting Started with Harness CD 1. Log into [Harness](https://app.harness.io/). 2. Select **Projects**, and then select **Default Project** {% hint style="warning" %} For the pipeline to run successfully, please follow the remaining steps as they are, including the naming conventions. {% endhint %} #### Delegate
What is the Harness Delegate? The Harness Delegate is a service that runs in your local network or VPC to establish connections between the Harness Manager and various providers such as artifacts registries, cloud platforms, etc. The delegate is installed in the target infrastructure, for example, a Kubernetes cluster, and performs operations including deployment and integration. Learn more about the delegate in the [Delegate Overview](/harness-ai/use-harness-platform/delegates/delegate/delegate-concepts/delegate-overview.md).
1. Under **Project Setup**, select **Delegates**. * Select **Delegates**. * Select **New Delegate**. For this tutorial, let's explore how to install a delegate using Docker. * In the command provided, `ACCOUNT_ID` and `MANAGER_ENDPOINT` are auto-populated values that you can obtain from the delegate installation wizard. * Replace **DELEGATE\_TOKEN** in the command with the token from the wizard. ```bash docker run -dit --cpus=1 --memory=2g \ -e DELEGATE_NAME=docker-delegate \ -e NEXT_GEN="true" \ -e DELEGATE_TYPE="DOCKER" \ -e ACCOUNT_ID=ACCOUNT_ID \ -e DELEGATE_TOKEN=DELEGATE_TOKEN \ -e MANAGER_HOST_AND_PORT=MANAGER_ENDPOINT harness/delegate:23.05.79310 ``` * Select **Verify** to verify that the delegate is installed successfully and can connect to the Harness Manager. * Select **Verify** to verify that the delegate is installed successfully and can connect to the Harness Manager. {% hint style="info" %} You can also follow the [Install Harness Delegate on Kubernetes or Docker](/harness-ai/troubleshooting-and-resources/tutorials/install-delegate.md) steps to install the delegate using the Harness Terraform Provider or a Kubernetes manifest. {% endhint %} #### Secrets
What are Harness secrets? Harness offers built-in secret management for encrypted storage of sensitive information. Secrets are decrypted when needed, and only the private network-connected Harness Delegate has access to the key management system. You can also integrate your own secret manager. To learn more about secrets in Harness, go to [Harness Secret Manager Overview](/harness-ai/use-harness-platform/secrets/secrets-management/harness-secret-manager-overview.md).
1. Under **Project Setup**, select **Secrets**. * Select **New Secret**, and then select **Text**. * Enter the secret name `harness_gitpat`. * For the secret value, paste the GitHub personal access token you saved earlier. * Select **Save**. 2. Under **Project Setup**, select **Secrets**. * Select **New Secret**, and then select **File**. * Enter the secret name `gcpsecret`. * For the secret value, upload the Google Cloud's account service key file for your service account, which you can download from your [GCP project](https://developers.google.com/workspace/guides/create-credentials#create_credentials_for_a_service_account). * Select **Save**. {% tabs %} {% tab title="UI" %} #### Connectors
What are connectors? Connectors in Harness enable integration with 3rd party tools, providing authentication and operations during pipeline runtime. For instance, a GitHub connector facilitates authentication and fetching files from a GitHub repository within pipeline stages. Explore connector how-tos [here](/harness-ai/use-harness-platform/connectors.md).
1. Create the **GitHub connector**. * Copy the contents of [github-connector.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/github-connector.yml) * In your Harness project in the Harness Manager, under **Project Setup**, select **Connectors**. * Select **Create via YAML Builder** and paste the copied YAML. * Assuming you have already forked the [harnesscd-example-apps](https://github.com/harness-community/harnesscd-example-apps/fork) repository mentioned earlier, replace **GITHUB\_USERNAME** with your GitHub account username in the YAML. * In `projectIdentifier`, verify that the project identifier is correct. You can see the Id in the browser URL (after `account`). If it is incorrect, the Harness YAML editor will suggest the correct Id. * Select **Save Changes** and verify that the new connector named **harness\_gitconnector** is successfully created. * Finally, select **Connection Test** under **Connectivity Status** to ensure the connection is successful. 2. Create the **GCP connector**. * Copy the contents of [gcp-connector.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/gcp-connector.yml). * In your Harness project, under **Project Setup**, select **Connectors**. * Select **Create via YAML Builder** and paste the copied YAML. * Select **Save Changes** and verify that the new connector named **gcpconnector** is successfully created. * Finally, select **Connection Test** under **Connectivity Status** to verify the connection is successful. #### Environment
What are Harness environments? Environments define the deployment location, categorized as **Production** or **Pre-Production**. Each environment includes infrastructure definitions for serverless functions, VMs, Kubernetes clusters, or other target infrastructures. To learn more about environments, go to [Environments overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/environments/environment-overview.md).
1. In your Harness project, select **Environments**. * Select **New Environment**, and then select **YAML**. * Copy the contents of [environment.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/environment.yml), paste it into the YAML editor, and select **Save**. * In your new environment, select the **Infrastructure Definitions** tab. * Select **Infrastructure Definition**, and then select **YAML**. * Copy the contents of [infrastructure-definition.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/infrastructure-definition.yml) and paste it into the YAML editor. * Replace `CLOUD PROJECT NAME` with your GCP project name. * Replace `REGION` with your GCP region name. * Select **Save** and verify that the environment and infrastructure definition are created successfully. #### Services
What are Harness services? In Harness, services represent what you deploy to environments. You use services to configure variables, manifests, functions, and artifacts. The **Services** dashboard provides service statistics like deployment frequency and failure rate. To learn more about services, go to [Services overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/services-overview.md).
1. In your Harness project, select **Services**. * Select **New Service**. * Enter the name `hello_world`. * Select **Save**, and then **YAML** (on the **Configuration** tab). * Select **Edit YAML**, copy the contents of [service.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/1st_gen/service.yml), and paste the into the YAML editor. * Replace `CLOUD PROJECT NAME` with your GCP project name. * Replace `CLOUD BUCKET NAME` with your GCP bucket name. * Select **Save**, and verify that the service **hello\_world** is successfully created. #### Pipeline
What are Harness pipelines? A pipeline is a comprehensive process encompassing integration, delivery, operations, testing, deployment, and monitoring. It can utilize CI for code building and testing, followed by CD for artifact/function deployment in production. A CD Pipeline is a series of stages where each stage deploys a service to an environment. To learn more about CD pipeline basics, go to [CD pipeline basics](/continuous-delivery/new-to-continuous-delivery/overview.md#pipeline).
1. In your Harness project, select **Pipelines**. * Select **Create a Pipeline**. * Enter the name `hello_world`. * Select **Inline** to store the pipeline in Harness. * Select **Start**. * In **Pipeline Studio**, select **YAML**. * Select **Edit YAML** and Paste the below Rolling deployment YAML.
What are Basic deployments? For Google Cloud Functions, the basic deployment execution strategy deploys the new function version and routes 100% of traffic from the old version to the new function version.
1. Copy the contents of [basic-pipeline.yml](https://github.com/harness-community/harnesscd-example-apps/blob/master/google_cloud_function/1st_gen/basic-pipeline.yml). 2. In your Harness pipeline YAML editor, paste the YAML. 3. Select **Save**. You can switch to the **Visual** pipeline editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% tab title="CLI" %} 1. Download and Configure Harness CLI. {% tabs %} {% tab title="MacOS" %} ```bash curl -LO https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-darwin-amd64.tar.gz tar -xvf harness-v0.0.25-Preview-darwin-amd64.tar.gz export PATH="$(pwd):$PATH" echo 'export PATH="'$(pwd)':$PATH"' >> ~/.bash_profile source ~/.bash_profile harness --version ``` {% endtab %} {% tab title="Linux" %} {% tabs %} {% tab title="ARM" %} ```bash curl -LO https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-linux-arm64.tar.gz tar -xvf harness-v0.0.25-Preview-linux-arm64.tar.gz ``` {% endtab %} {% tab title="AMD" %} ```bash curl -LO https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-linux-amd64.tar.gz tar -xvf harness-v0.0.25-Preview-linux-amd64.tar.gz ``` {% endtab %} {% endtabs %} {% endtab %} {% tab title="Windows" %} a. Open Windows Powershell and run the command below to download the Harness CLI. ``` Invoke-WebRequest -Uri https://github.com/harness/harness-cli/releases/download/v0.0.25-Preview/harness-v0.0.25-Preview-windows-amd64.zip -OutFile ./harness.zip ``` b. Extract the downloaded zip file and change directory to extracted file location. c. Follow the steps below to make it accessible via terminal. ``` $currentPath = Get-Location [Environment]::SetEnvironmentVariable("PATH", "$env:PATH;$currentPath", [EnvironmentVariableTarget]::Machine) ``` d. Restart terminal. {% endtab %} {% endtabs %} 2\. Clone the Forked **harnesscd-example-apps** repo and change directory. ```bash git clone https://github.com/GITHUB_ACCOUNTNAME/harnesscd-example-apps.git cd harnesscd-example-apps ``` {% hint style="info" %} Replace `GITHUB_ACCOUNTNAME` with your GitHub Account name. {% endhint %} 3. Log in to Harness from the CLI. ```bash harness login --api-key --account-id HARNESS_API_TOKEN ```

Replace HARNESS_API_TOKEN with Harness API Token that you obtained during the prerequisite section of this tutorial.

What are connectors? Connectors in Harness enable integration with 3rd party tools, providing authentication and operations during pipeline runtime. For instance, a GitHub connector facilitates authentication and fetching files from a GitHub repository within pipeline stages. For more details, go to [Connectors](/harness-ai/use-harness-platform/connectors.md).
1. Create the **GitHub connector**. 1. In `projectIdentifier`, verify that the project identifier is correct. You can see the Id in the browser URL (after `account`). If it is incorrect, the Harness YAML editor will suggest the correct Id. 2. Now create the **GitHub connector** using the following CLI command: ``` harness connector --file "/google_cloud_function/github-connector.yml" apply ``` 2. Create the **GCP connector**. 1. In `projectIdentifier`, verify that the project identifier is correct. You can see the Id in the browser URL (after `account`). If it is incorrect, the Harness YAML editor will suggest the correct Id. 2. Now create the **AWS Connector** using the following CLI command: ``` harness connector --file "/google_cloud_function/gcp-connector.yml" apply ``` #### Environment
What are Harness environments? Environments define the deployment location, categorized as **Production** or **Pre-Production**. Each environment includes infrastructure definitions for serverless functions, VMs, Kubernetes clusters, or other target infrastructures. To learn more about environments, go to [Environments overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/environments/environment-overview.md).
1. Use the following CLI Command to create **Environments** in your Harness project: ``` harness environment --file "/google_cloud_function/environment.yml" apply ``` 2. In your new environment, add **Infrastructure Definitions** using the following CLI command: ``` harness infrastructure --file "/google_cloud_function/infrastructure-definition.yml" apply ``` #### Services
What are Harness services? In Harness, services represent what you deploy to environments. You use services to configure variables, manifests, functions, and artifacts. The **Services** dashboard provides service statistics like deployment frequency and failure rate. To learn more about services, go to [Services overview](/continuous-delivery/use-continuous-delivery/cd-building-blocks/services/services-overview.md).
1. Use the following CLI command to create **Services** in your Harness Project. ``` harness service -file "/google_cloud_function/1st_gen/service.yml" apply ``` #### Pipeline
What are Basic deployments? For Google Cloud Functions, the basic deployment execution strategy deploys the new function version and routes 100% of traffic from the old version to the new function version.
1. CLI Command for basic deployment: ``` harness pipeline --file "/google_cloud_function/1st_gen/basic-pipeline.yml" apply ``` 2. You can switch to the **Visual** pipeline editor and confirm the pipeline stage and execution steps as shown below.

Click to view full size image

{% endtab %} {% endtabs %} Finally, it's time to execute your pipeline. 1. Select **Run**, and then select **Run Pipeline** to initiate the deployment. * Observe the execution logs as Harness deploys the workload and checks for steady state. * After a successful execution, you can check the deployment on your Google Cloud Function console. #### Congratulations!🎉 You've just learned how to use Harness CD to deploy an application using a Google Cloud Functions gen 1 to Google Cloud. Keep learning about Harness GitOps. Create a GitOps ApplicationSet and PR Pipeline in Harness GitOps by following this [guide](/continuous-delivery/use-gitops/applicationsets/harness-git-ops-application-set-tutorial.md). {% endtab %} {% endtabs %}