The server could not verify that you are authorized to access the URL requested. You either si 4 > cistfile xt hosted with @ by GitHub view raw Testing the protected application endpoint with curl — HTTP 401 Now, if you remember, the /hello endpoint is protected with a Basic Auth mechanism, and the reason for this is to demonstrate how we can make use of environment variables on Cloud Run. To fix this problem, we can make use of some scripts versioned into our repository. If you have gone through the steps to run and test the application locally, as described in the application README file, you'll remember of the scripts/hash_value.py script, which we can use to hash values in the SHA-512 form. Earlier in this article, we talked about the require_api_key decorator, which is used to secure our /hello endpoint with Basic Auth. Remember that, under the hood, this decorator reads the HASHED_API_KEY environment variable, hashes the received x-api-key HTTP header value with SHA-512 and compares both values to decide whether or not to allow the request to. proceed. To set the HASHED_API_KEY environment variable, follow these steps: nips medium, comic. thow4o-setup-2- deployment pipeine-on-gcp-with Cloud Run < Deploy revision to pipeline-demo (us-central1) Aservice can have multiple revisions. The configurations of each revision are immutable. Container image URL * gerio/iluz-tutorials/pipeline-demo:50ec691 ‘SELECT gcrio/cloudcunvhelo Should listen for HTTP requests on $PORT and not rly on local state, How to build a container? Advanced settings CONTAINER VARIABLES CONNECTIONS: Store and consume secrets using Secret Manager Environment variables Name Value HASHED_APLKEY d404559'602eab6fd602ac7680dac + ADD VARIABLE Setting environment variables manually * Click the DEPLOY button; Wait for the application to be deployed and retest it with the following curl command: 1 2 3 a 5 6 7 8 npe:simedium.convic-thhow-o-sel-up-2-deployment-pipel S curl -4\ > cH txcapi-key: 1236" \. > “https://pipeline-dero-pmrayanvha-uc.a.run.app/hello* HTTP/2 200 content-type: application/json date: Sat, 16 May 2028 21:48:25 GMT server: Google Frontend content-length: 18 .on-gep-with-cloud-builé-containeregisty-and-cloud-run-739911Sb7 704 aia1019123, 6.04PM How to Set Up @ Deployment Pipeline on Google Cloud wth Cloud Bulle, Container Registry and Cloud Run |by Wwam Luz | CIST fag} ma=zo¥cowe,n4-co= 1484 j MaSe>¥eNOY,N9-Iu>e= ads j MaRco¥LOOe,Ns-WEDE= t 10 3 {hello" world") < > sistfile xt hosted with @ by GitHub view raw Testing the protected application endpoint with curl — HTTP 200 Notice how we now get a 200 response back containing our “Hello, world” JSON. Automating the environnment variable configuration Alternatively, if you have gcloud configured locally, you can use the scripts/set_env_vars.sh script to configure the environment variable configuration. To do so, run the following command from inside the scripts folder: $ -/set_env_vars.sh Enter the Cloud Run Service nare: pipeline-deno ¥ Deploying... Done. Y creating Revision. Done. Service [pipeline-deno] revision [pipeline-deno-800e4-hec] has been deployed and is serving 10@ px 1 2 3 4 5 ¥ Routing traffic. 6 7 4 » sistfilettxt hosted with @ by GitHub view raw Automating the environment variable configuration The command will prompt for the service name to be updated and for the unhashed value of the API Key. It will then update the Cloud Run service with the hashed value for the provided API Key: HI /bin/bash 1 2 3 read -p “Enter the Cloud Run Service name: “ SERVICE NAME 4 read -5 -p “Enter the APT KEY: * APT_KEY !ntps:imecium.comi-thow-to.sel-up-a-deployment pipeline-on-gep-with-cloud-bult-containeregisty-and-cloud-run-739911Sb7 704 251921019723, 6:04 Pmt How to Set Up a Deployment Pipeline on Google Cloud with Cloud Build, Container Registy and Cloud Run | by Wwam Luz | CI8T | HASHED_APT_KEV=" ./hash_value.py --value "S{API_KEY} 6 7 8 gcloud run \ 9 services update $SERVICE_NAME \, 10 =-region us-centrala \ 11 ~-platform managed \ 12 --update-env-vars HASHED_API_KEY-SHASHED_API_KEY setenv_vars sh hosted with @ by GitHub view raw The script to update the service environment variables Clean-up To undo the changes done while following this tutorial, make sure to: * Delete the deployed Cloud Run service; * Delete the Container Registry saved images; * Delete the Cloud Build configured triggers; * Disconnect any connected repositories. Final Thoughts In this tutorial, we have gone through the process of setting up a deployment pipeline powered by GitHub, Cloud Build, Container Registry and Cloud Run. The pipeline was configured to be triggered everytime new code was pushed into the master branch of the connected repository. Once that happens, the nips medium, comic. thow4o-setup-2- deployment pipeine-on-gcp-with