Note that environment variables defined in app.yaml aren’t intended to be made available on the Container Builder <https://cloud.google.com/container-builder/> during the App Engine flexible deployment process. One of the often used reasons for environment variables is for secrets. They are then being persisted for anyone who can access the image at a later date.
A workaround can be writing your own Build Requests <https://cloud.google.com/container-builder/docs/how-to/writing-build-requests> for Container Builder, which allows you to specify environment variables, and then deploying the built images to App Engine <https://cloud.google.com/container-registry/docs/using-with-google-cloud-platform#deploying_to_app_engine> . You can also pass these variables to Cloud Builder in the `env` portion of the BuildStep <https://cloud.google.com/cloud-build/docs/api/reference/rest/v1/projects.builds#Build.BuildStep> that needs them. For the issue on the secure handler, I recommend to post your full detailed question <https://stackoverflow.com/help/how-to-ask> to Stack Overflow <https://cloud.google.com/support/docs/stackexchange>, using the supported Cloud tags since Google Groups are reserved for general Google Cloud Platform-end product discussions and not for technical questions. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send email to google-appengine@googlegroups.com. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/5e8dca31-d766-4d0a-86fa-1ab79dab550b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
