如何在 Google App Engine 标准环境中使用 Google Cloud Build 或其他方法设置环境变量？

Question

Is there anyway to inject environment variables from Cloud Build into the App Engine Standard environment?

I do not want to push my environment variables to GitHub inside the app.yaml or .env . Thus, when Cloud Build pulls and deploys it is missing the .env file and the server is unable to complete some requests.

I am trying to avoid using Datastore as the async nature of Datastore will make the code a lot more messy. I tried to use encrypted secrets found here , but that doesn't seem to work as I added the secrets to app deploy and they do not make their way into the deployment, so I assume this is not the use case for Cloud Build.

I also tried the tutorial here , to import the .env file into App Engine Standard from storage, but since Standard does not have local storage I assume it goes into the void.

So is there anyway to inject the .env into App Engine Standard environment without using Datastore, or committing app.yaml or .env to change control? Potentially using Cloud Build, KMS, or some type of storage?

Here is what I tried for cloudbuild.yaml :

steps:
- name: "gcr.io/cloud-builders/gcloud"
  args: ["app", "deploy"]
  secretEnv: ['SECRET1', 'SECRET2', 'SECRET3', 'SECRET4', 'SECRET5']
timeout: "1600s"

secrets:
- kmsKeyName: projects/<Project-Name>/locations/global/keyRings/<Key-Ring-Name>/cryptoKeys/<Key-Name>
  secretEnv:
    SECRET1: <encrypted-key-base64 here>
    SECRET2: <encrypted-key-base64 here>
    SECRET3: <encrypted-key-base64 here> 
    SECRET4: <encrypted-key-base64 here> 
    SECRET5: <encrypted-key-base64 here>

Answer 1

Here is a tutorial on how to securely store env vars in your cloud build (triggers) settings and import them into your app.

Basically there are three steps:

1. Add your env vars to the 'variables' section in one of your build trigger settings

   Screenshot of where to add variables in build triggers

   By convention variables set in the build trigger must begin with an underscore (_)

2. Configure cloudbuild.yaml (on the second step in the code example) to read in variables from your build trigger, set them as env vars, and write all env vars in a local .env file

   Add couldbuild.yaml (below) to your project root directory

 steps: - name: node:10.15.1 entrypoint: npm args: ["install"] - name: node:10.15.1 entrypoint: npm args: ["run", "create-env"] env: - 'MY_SECRET_KEY=${_MY_SECRET_KEY}' - name: "gcr.io/cloud-builders/gcloud" args: ["app", "deploy"] timeout: "1600s"

Add create-env script to package.json

 "scripts": { "create-env": "printenv > .env" },

3. Read env vars from .env to your app (config.js)

   Install dotenv package

   npm i dotenv -S

   Add a config.js to your app

 // Import all env vars from .env file require('dotenv').config() export const MY_SECRET_KEY = process.env.MY_SECRET_KEY console.log(MY_SECRET_KEY) // => Hello

Done! Now you may deploy your app by triggering the cloud build and your app will have access to the env vars.

Answer 2

I have another solution, if someone is still interested in this. This should work on all languages, because environment variables are added directly into app.yaml file

1. Add substitution variable in build trigger (as described in this answer ).

2. Add environment variables to app.yaml in a way they can be easily substituted with build trigger variables. Like this:

    env_variables:
     SECRET_KEY: %SECRET_KEY%

3. Add a step in cloudbuild.yaml to substitute all %XXX% variables inside app.yaml with their values from build trigger.

    - name: 'gcr.io/cloud-builders/gcloud'
      entrypoint: bash
      args:
      - '-c'
      - |
      sed -i 's/%SECRET_KEY%/'${_SECRET_KEY}'/g' app.yaml
      gcloud app deploy  app.yaml

Answer 3

The highfivebrian answer is great, but I'm adding my slightly different solution.

1). In the root project folder we need the cloudbuild.yaml file but I'll call it buildsetttings.yaml , because first one name have a problem

In buildsetttings.yaml I added this code:

 steps: - name: node entrypoint: npm args: ['install'] - name: node entrypoint: npm env: - 'DB_URL=${_DB_URL}' - 'SENDGRID_API_KEY=${_SENDGRID_API_KEY}' - 'CLIENT_ID=${_CLIENT_ID}' args: ['run', 'create-app-yaml'] - name: 'gcr.io/cloud-builders/gcloud' args: ['app', 'deploy']

buildsetttings.yaml will be create app.yaml file in the Cloud Build, using a npm create-app-yaml command. Tip: app.yaml file we will then use to deploy our app to GCP App Engine.

2). In the root folder(near buildsetttings.yaml) we need to create create-app-yaml.js which will run in Cloud Build after it is called from buildsetttings.yaml.

In buildsetttings.yaml I added this code:

 require('dotenv').config(); const fs = require('fs'); const appYamlContent = `runtime: nodejs14 env_variables: DB_URL: ${process.env.DB_URL} SENDGRID_API_KEY: ${process.env.SENDGRID_API_KEY} CLIENT_ID: ${process.env.CLIENT_ID}`; fs.writeFileSync('./app.yaml', appYamlContent);

This code using a npm package dotenv (add it to package.json) and get variables from Cloud Build Trigger Variables and create with they app.yaml file.

3). app.yaml file was created in the Cloud build and our last step(name: 'gcr.io/cloud-builders/gcloud') in the buildsetttings.yaml, using app.yaml file, deploy the project to the Google Cloud App Engine.

Success!

In short, it works like this : buildsetttings.yaml run "create-app-yaml.js" in the Cloud Build, after which dynamically creates an app.yaml file by adding variables from Cloud Build Trigger Variables, then makes a deployment in the App Engine.

Notes:

• Delete the file app.yamlin from you project, because it will be create dynamically in the Cloud Build. Also delete cloudbuild.yaml file, because instead we use buildsetttings.yaml.

• package.json:

• Cloud Build Trigger Variables:

Answer 4

As of 2020/11/13 . It seem like .env will work only at that step and in the next step an invisible .env will no longer there.

If you get stuck do try consume that printed .env it in 1 step like this...
in cloudbuild.yaml

# [START cloudbuild_yarn_node]
steps:
  # Install
  - name: node
    entrypoint: yarn
    args: ["install"]
  # Build
  - name: node
    entrypoint: yarn
    env:
      - "FOO=${_FOO}"
    args: ["env-build"]

and in package.json add this

{
  "scripts": {
    "env-build": "printenv > .env && yarn build",
  }
}

in index.js

require('dotenv').config();
console.log(process.env.FOO);

Took me an hour to figure this out.

Answer 5

First, I created secret using gcp secret manager and uploaded my env file there. Second, I called the secret in cloudbuild.yaml on run time and created a file with name of '.env' using echo.

Example

steps: 
- id: "Injecting ENV"
  name: 'gcr.io/cloud-builders/gcloud'
  entrypoint: bash
  args:
      - '-c'
      - |
        echo $$ENV > .env
  secretEnv: ['ENV']


availableSecrets: 
  - versionName: projects/<Project-Name>/secrets/environment-variables/versions/1
    env: 'ENV'
timeout: 900s

Answer 6

Based on your preferences that you have highlighted (Cloud Build, KMS). The Google Secrets link that you had mentioned involves storing sensitive data at build or runtime using Cloud KMS : KeyRing and CryptoKey. However, Google offers other Secret Management Solutions using Cloud KMS as well.

Here are a couple of other options you can use while storing Secrets :

Option 1 : You can store Secrets in code that are encrypted with a key from Cloud KMS. (This is typically used by encrypting your secret at the application layer.)

Benefit: Provides a layer of security from insider threats because it restricts access to the code with a corresponding key .

[You can find some additional information about these options on the Google Documentation here .]

Option 2: You can Store Secrets inside a Google Storage Bucket where your data is at rest encryption. (Similar to option 1 this has the ability to limit access to secrets to a small group of Developers.)

Benefit: Storing your secrets in a separate location ensures that if a breach of your code repository has occurred , your secrets may still be protected .)

[Note: Google recommends that you use two projects for proper separation of duties . One project will use Cloud KMS to manage the keys and the other project will use Cloud Storage to store the secrets.]

If the options listed above still do not meet your needs, I have found a StackOverflow question that shares a similar objective as your project. (ie: Storing environment variables in GAE without Datastore)

The solution provided on this link illustrates the use of storing keys in a client_secrets.json file that gets excluded when uploading to git by listing it in .gitignore. You can find some Google examples (Python) of usage here .