Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue #11745 - fix the environment var for the GAE Instance in id-manager.xml #11797

Merged
merged 3 commits into from
May 28, 2024

Conversation

lachlan-roberts
Copy link
Contributor

Issue #11745

The GAE_MODULE_INSTANCE doesn't seem to be available anymore for AppEngine.

The GAE documentation says that the GAE_INSTANCE env var contains "the ID of the instance on which your service is currently running" (see https://cloud.google.com/appengine/docs/standard/java-gen2/runtime#environment_variables).

Also the jetty-runtime image for GAE Flexible uses the GAE_INSTANCE env var for this purpose (see https://github.com/GoogleCloudPlatform/jetty-runtime/blob/248859491c1df0f8675bb4ee1252225b0f53c6ce/jetty9/src/main/docker/50-jetty.bash#L4-L7).

…ager.xml

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
…ager.xml

Signed-off-by: Lachlan Roberts <lachlan@webtide.com>
@janbartel
Copy link
Contributor

@lachlan-roberts I think you should merge this - the build failure is something to do with flakey mongo test.

@lachlan-roberts
Copy link
Contributor Author

@janbartel I think jetty-12.0.x has some branch protection so that I can't merge if it is a failing build.

@janbartel janbartel merged commit bc03176 into jetty-12.0.x May 28, 2024
6 of 9 checks passed
@janbartel janbartel deleted the jetty-12.0.x-11745-sessionIdManagerWorkerName branch May 28, 2024 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Status: ✅ Done
Development

Successfully merging this pull request may close these issues.

None yet

2 participants