-
Notifications
You must be signed in to change notification settings - Fork 3
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
Release 8.1.0 breaks server startup #449
Comments
8.0.0 works? I can't see from the referenced PR why 8.1.0 would fail... |
Yep, it is surprising! I intend to investigate the cause as soon as possible today, I'm afraid that PR #447 may hide some changes in it's diff - for instance, for |
This fixes #449, the problem with server startup that was released with play-secret-rotation v8.1.0.
This reverts commit 0058416, and updates to https://github.com/guardian/play-secret-rotation/releases/tag/v8.2.1, which fixes the server-startup problem.
Unfortunately v8.1.0, broke server startup, and should not be used. The release contained this single change:
The error only occurs when Play is run in 'production' mode - typically, when we run Play as developers, we run Play in 'dev' mode, with the
run
command - in this mode, you have things like hot-code-reload, and the application-secret checks are more lenient. However, those behaviours aren't desirable in Production, so when a Play app is deployed, we get those additional checks.We can simulate Production behaviour in dev by running with
runProd
rather thanrun
, eg, for Ophan:The error given is:
The text was updated successfully, but these errors were encountered: