Append env_vars in all kokoro build configuration files (*.cfg in .kokoro/) which contain an env_vars (key: JOB_TYPE, value: integration)

When you want to append the environment variable too all templated .cfg which has an env_vars (key: JOB_TYPE, value: integration), follow the steps below:

1. Create a partial file in the repository root directory.
   Note that the file extension should be .yaml.
2. Write customization entries in the partial file.
3. Create a pull request containing changes in step 1 - 2
4. Confirm the customizations appear in the configuration file in the same pull request after the OwlBot post processor runs.

Modify default env_vars in Kokoro build templates

You don’t need to modify existing env_vars defined in the templates because if there are multiple env_vars with the same key, the last value will be used.

Please refer to Maps in proto 3 language guide.

Example

Append env_vars in configuration files with an env_vars (key: JOB_TYPE, value: integration)

1. Add a partial file .integration-partials.yaml to the repository root.
2. In .integration-partials.yaml, add the following section:

integration: |
  env_vars: {
    key: "INTEGRATION_TEST_ARGS"
    value: "-P bigtable-emulator-it"
  }
  
  env_vars: {
    key: "GCLOUD_PROJECT"
    value: "gcloud-devel"
  }

3. Create a pull request containing the changes in step 1 - 2.

After the change

The following section will be appended to

• .kokoro/nightly/integration.cfg
• .kokoro/nightly/java11-integration.cfg
• .kokoro/presubmit/integration.cfg

env_vars: {
  key: "INTEGRATION_TEST_ARGS"
  value: "-P bigtable-emulator-it"
}

env_vars: {
  key: "GCLOUD_PROJECT"
  value: "gcloud-devel"
}

Because these files contain env_vars (key: JOB_TYPE, value: integration)

For env_var entry with key GCLOUD_PROJECT, the default value is overwritten by customized value (gcloud-devel) that appears later in the file.

Fix #1798.