Skip to content

Restart app on Doppler config changes via doppler run --watch #143

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.

Sign up for GitHub

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

Merged
SibeiC merged 1 commit into from
Jun 12, 2026
Merged

Restart app on Doppler config changes via doppler run --watch #143

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion entrypoint.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,4 +5,9 @@ set -eu
# --fallback keeps restarts working if api.doppler.com is briefly unreachable: doppler
# itself writes/refreshes this encrypted file on every successful fetch (it need not
# pre-exist) and only reads it when the API is unreachable.
exec doppler run --fallback /opt/api-server/doppler-fallback.json -- java -jar api-server.jar
# --watch (BETA) restarts the JVM in place whenever the Doppler config changes, so
# app-only secrets rotate without touching the box. Batch multi-secret rotations into
# one `doppler secrets set K1=… K2=…` call (each change event = one restart), and
# rotate nginx/p12-coupled secrets (proxy secret, keystore password) via an ansible
# re-converge instead — a watch restart alone would leave nginx/p12 out of sync.
exec doppler run --watch --fallback /opt/api-server/doppler-fallback.json -- java -jar api-server.jar
Loading