Go 1.11: what is the recommended way to include env_variables in app.yaml?

[Jonathan Ingram]

Prior to Go 1.11 I would include environment specific env vars in my app.yaml like this:

includes:

  - ../env/env.yaml

It allowed me to deploy to different environments (staging, prod) and also for different tenants.

With Go 1.11, includes has been removed and is not supported anymore.

Is the recommended way to just have an app.yaml for each environment/tenant combination? In this way, if I have, say, 10 handlers that are shared across my app, will I just have to duplicate them?

Alternatively, do I have to do some templating in my CI flow and dynamically generate each app.yaml?

[Steren Giannini]

Hi Jonathan,

Let me ask internally why includes has been removed from the new runtimes. Your use case seems quite relevant to me.

Steren

Product Manager

--
You received this message because you are subscribed to the Google Groups "google-appengine-go" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-appengin...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine-go/864a91e3-c27b-49a2-b832-bbec447712cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[benjam...@paymentsense.com]

Hi Steren,

Where you able to find out why it's been removed? We're looking at a similar multi-environment deployment.

Thanks,

Ben

On Sunday, 11 November 2018 22:37:08 UTC, Steren Giannini wrote:

Hi Jonathan,

Let me ask internally why includes has been removed from the new runtimes. Your use case seems quite relevant to me.

Steren

Product Manager

On Sun, Nov 11, 2018 at 2:28 PM Jonathan Ingram <jonatha...@gmail.com> wrote:

Prior to Go 1.11 I would include environment specific env vars in my app.yaml like this:

includes:

  - ../env/env.yaml

It allowed me to deploy to different environments (staging, prod) and also for different tenants.

With Go 1.11, includes has been removed and is not supported anymore.

Is the recommended way to just have an app.yaml for each environment/tenant combination? In this way, if I have, say, 10 handlers that are shared across my app, will I just have to duplicate them?

Alternatively, do I have to do some templating in my CI flow and dynamically generate each app.yaml?

--
You received this message because you are subscribed to the Google Groups "google-appengine-go" group.

To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine-go+unsub...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine-go/864a91e3-c27b-49a2-b832-bbec447712cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

This message may contain information from Paymentsense Ltd which is confidential or privileged. If you are not the intended recipient, please advise the sender immediately by reply email and delete this message and any attachments without retaining a copy. Any views expressed in this message are those of the individual sender, except where the sender specifies and with authority.

[daniel fischer]

You can solve this using Cloud Build and before running the deploy command copy over a file from block storage or decrypt a key from google kms.