Need to make substitutions in app.yaml for local/remote testing on a per-test basis

[janbartel]

For testing sessions, I need to be able to put an env var into app.yaml (eg SESSIONS: 'datastore'). This env var shouldn't be there when local tests are run (unless the local docker execution is set up with the correct gcloud project properties etc). This substitution should really only be done when a specific test - eg RemoteSessionIntegerationTest - is run. I can't see how to accomplish this with the existing structure. Is there any way to accommodate this?

[meltsufin]

@janbartel The maven property substitutions seems to work in app.yaml at a profile level if you just specify the properties under the corresponding profile. However, it sounds like you want to have properties on a per test basis. Is that correct?
In that case, it might be better to just create more test apps specifically for testing various session configurations.

[jmcc0nn3ll]

As @meltsufin notes, unless a configured container is meant to be deployed with different session stores dynamically then this datastore test case should be bundled up in a test-session-datastore(?) artifact and execute accordingly.

Then the actual test method should be annotated with @RemoteOnly, at least until there is a reasonable configuration that allows containers deployed other places (locally, etc) to leverage that session store.