Tips for setting up GCP Cloud Build.
Set Secret Env Variable for Cloud Build This is an introduction to using environment variables that you don’t want to leak in Cloud Build.
gcloud kms keyrings create [KEYRING NAME] \     --location=global \     --project=[PROJECT NAME] gcloud kms keys create PASSWORD \   --location=global \   --keyring=[KEYRING NAME] \   --purpose=encryption \   --project=[PROJECT NAME] gcloud kms keys add-iam-policy-binding \     DOCKER_USER_NAME --location=global --keyring=[KEYRING NAME] \     --member=serviceAccount:[ACCOUNT ID]@cloudbuild.gserviceaccount.com \     --project=[PROJECT NAME] \     --role=roles/cloudkms.cryptoKeyDecrypter    echo  -n $PASSWORD  | gcloud kms encrypt \  --plaintext-file=- \   --ciphertext-file=- \   --location=global \   --keyring=[KEYRING NAME] \   --project=[PROJECT NAME] \   --key=PASSWORD | base64 
Register the completed string in cloudbuild.yml.
steps:   - name:  'gcr.io/cloud-builders/docker'     entrypoint:  'bash'     secretEnv:  ['PASSWORD']     args:     -  '-c'     -  |       echo "Do something" secrets:   - kmsKeyName:  projects/[PROJECT  NAME]/locations/global/keyRings/[KEYRING  NAME]/cryptoKeys/PASSWORD     secretEnv:       PASSWORD:  [ENCRIPTED  TEXT] 
😼 References 
                
    
    
    
                
    🖥 Recommended VPS Service 
    
    VULTR Check Benchmark Results