RetroSearch Browse

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/functions/docs/quickstart below:

Quickstart: Deploy a Cloud Run function using the gcloud CLI | Cloud Run Documentation

Stay organized with collections Save and categorize content based on your preferences.

Quickstart: Deploy a Cloud Run function using the gcloud CLI

This page shows you how to deploy an HTTP Cloud Run function using the gcloud CLI.

Before you begin

Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.
Install the Google Cloud CLI.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
To initialize the gcloud CLI, run the following command:
```
gcloud init
```
Create or select a Google Cloud project.
Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.
- Create a Google Cloud project:
```
gcloud projects create PROJECT_ID
```
  Replace PROJECT_ID with a name for the Google Cloud project you are creating.
- Select the Google Cloud project that you created:
```
gcloud config set project PROJECT_ID
```
  Replace PROJECT_ID with your Google Cloud project name.
Verify that billing is enabled for your Google Cloud project.

Enable the Artifact Registry, Cloud Build, Cloud Run Admin API, and Cloud Logging APIs:

gcloud services enable artifactregistry.googleapis.com cloudbuild.googleapis.com run.googleapis.com logging.googleapis.com

Grant roles to your user account. Run the following command once for each of the following IAM roles: roles/run.sourceDeveloper, roles/run.admin, roles/logging.viewer
```
gcloud projects add-iam-policy-binding PROJECT_ID --member="user:USER_IDENTIFIER" --role=ROLE
```
Replace the following:
- PROJECT_ID: your project ID.
- USER_IDENTIFIER: the identifier for your user account—for example, myemail@example.com.
- ROLE: the IAM role that you grant to your user account.
Install the Google Cloud CLI.
Note: If you installed the gcloud CLI previously, make sure you have the latest version by running gcloud components update.
If you're using an external identity provider (IdP), you must first sign in to the gcloud CLI with your federated identity.
To initialize the gcloud CLI, run the following command:
```
gcloud init
```
Create or select a Google Cloud project.
Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.
- Create a Google Cloud project:
```
gcloud projects create PROJECT_ID
```
  Replace PROJECT_ID with a name for the Google Cloud project you are creating.
- Select the Google Cloud project that you created:
```
gcloud config set project PROJECT_ID
```
  Replace PROJECT_ID with your Google Cloud project name.
Verify that billing is enabled for your Google Cloud project.

Enable the Artifact Registry, Cloud Build, Cloud Run Admin API, and Cloud Logging APIs:

gcloud services enable artifactregistry.googleapis.com cloudbuild.googleapis.com run.googleapis.com logging.googleapis.com

Grant roles to your user account. Run the following command once for each of the following IAM roles: roles/run.sourceDeveloper, roles/run.admin, roles/logging.viewer
```
gcloud projects add-iam-policy-binding PROJECT_ID --member="user:USER_IDENTIFIER" --role=ROLE
```
Replace the following:
- PROJECT_ID: your project ID.
- USER_IDENTIFIER: the identifier for your user account—for example, myemail@example.com.
- ROLE: the IAM role that you grant to your user account.
To set the default project for your Cloud Run service:
```
 gcloud config set project PROJECT_ID
```
Replace PROJECT_ID with the name of the project you created for this quickstart.
If you are under a domain restriction organization policy restricting unauthenticated invocations for your project, you will need to access your deployed service as described under Testing private services.
Make sure that you have the Service Account User role granted on the service identity. By default, the service identity is the Compute Engine default service account.
Grant the roles
To grant access on the service identity resource, use the gcloud iam service-accounts add-iam-policy-binding command, replacing the highlighted variables with the appropriate values:
```
      gcloud iam service-accounts add-iam-policy-binding SERVICE_ACCOUNT_EMAIL \
          --member="PRINCIPAL" \
          --role="roles/iam.serviceAccountUser"
      
```
Replace the following:
- SERVICE_ACCOUNT_EMAIL: the service account email address you are using as the service identity, such as:
  - The Compute Engine default service account: PROJECT_NUMBER-compute@developer.gserviceaccount.com
  - A service account that you created: SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com
- PRINCIPAL: the user identifier. This is typically the email address for a Google Account.
Grant the Cloud Build service account the following IAM role. Click to view required roles for the Cloud Build service account
Cloud Build automatically uses the Compute Engine default service account as the default Cloud Build service account to build your source code and Cloud Run resource, unless you override this behavior. For Cloud Build to build your sources, ask your administrator to grant Cloud Run Builder (roles/run.builder) to the Compute Engine default service account on your project:
```
  gcloud projects add-iam-policy-binding PROJECT_ID \
      --member=serviceAccount:PROJECT_NUMBER-compute@developer.gserviceaccount.com \
      --role=roles/run.builder
  
```
Replace PROJECT_NUMBER with your Google Cloud project number, and PROJECT_ID with your Google Cloud project ID. For detailed instructions on how to find your project ID, and project number, see Creating and managing projects.

Granting the Cloud Run builder role to the Compute Engine default service account takes a couple of minutes to propagate.
Note:
The iam.automaticIamGrantsForDefaultServiceAccounts organization policy constraint prevents the Editor role from being automatically granted to default service accounts. If you created your organization after May 3, 2024, this constraint is enforced by default.

We strongly recommend that you enforce this constraint to disable the automatic role grant. If you disable the automatic role grant, you must decide which roles to grant to the default service accounts, and then grant these roles yourself.

If the default service account already has the Editor role, we recommend that you replace the Editor role with less permissive roles.To safely modify the service account's roles, use Policy Simulator to see the impact of the change, and then grant and revoke the appropriate roles.

Write the sample function

To write an application, follow these steps:

Node.js

Create a new directory named helloworld and change directory into it:
```
   mkdir helloworld
   cd helloworld
```
Create a package.json file in the helloworld directory to specify Node.js dependencies:
Create an index.js file in the helloworld directory with the following Node.js sample:

Python

Create a new directory named helloworld and change directory into it:
```
   mkdir helloworld
   cd helloworld
```
Create a requirements.txt file in the helloworld directory, to specify Python dependencies:

This adds packages needed by the sample.
Create a main.py file in the helloworld directory with the following Python sample:

Create a new directory named helloworld and change directory into it:
```
   mkdir helloworld
   cd helloworld
```
Create a go.mod file to declare the go module:
Create an hello_http.go file in the helloworld directory with the following Go code sample:

Java

Create a new directory named helloworld and change directory into it:
```
   mkdir helloworld
   cd helloworld
```

Create the following project structure to contain the source directory and source file:

mkdir -p ~/helloworld/src/main/java/functions
touch ~/helloworld/src/main/java/functions/HelloWorld.java

Update the HelloWorld.java file with the following Java code sample:
Create a pom.xml file in the helloworld directory, and add the following Java dependencies:

Ruby

Create a new directory named helloworld and change directory into it:
```
   mkdir helloworld
   cd helloworld
```
Create a file named app.rb and paste the following code into it:
Create a file named Gemfile and copy the following into it:
If you don't have Bundler 2.0 or greater installed, install Bundler.
Generate a Gemfile.lock file by running:
```
bundle install
```

PHP

Create a new directory named helloworld and change directory into it:
```
   mkdir helloworld
   cd helloworld
```
Create a file named index.php and paste the following code into it:
If you aren't using Cloud Shell, create a composer.json file and paste the following code into it:

.NET

Install .NET SDK.
From the console, create a new empty web project using the dotnet command.
```
dotnet new web -o helloworld-csharp
```
Change directory to helloworld-csharp:
Replace the sample code in the project file helloworld-csharp.csproj with the following:
Replace the sample code in Program.cs file with the following:

Deploy the function

Important: This quickstart assumes that you have owner or editor roles in the project you are using for the quickstart. Otherwise, refer to the Cloud Run Source Developer role for the required permissions for deploying a Cloud Run resource from source.

To deploy your Cloud Run function, follow these steps:

Deploy the function by running the following command in the directory that contains the sample code:

Node.js

gcloud run deploy nodejs-http-function \
      --source . \
      --function helloGET \
      --base-image nodejs22 \
      --region REGION \
      --allow-unauthenticated