Handle api SIGTERM gracefully #368
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 6 commits
December 15, 2022 06:59
added 2 commits
December 20, 2022 10:13
Base automatically changed from
enhancement/handle-SIGTERM-gracefully-C-277
to
main
December 21, 2022 07:13
themarolt
deleted the
enhancement/handle-SIGTERM-gracefully-api-C-333
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes proposed ✍️
Checklist ✅
Feature,Enhancement, orBug.Environment variables have been updated:Local frontend configuration:frontend/.env.dist.local,frontend/.env.dist.composed.Local backend:backend/.env.dist.local,backend/.env.dist.composed.Configuration docs have been updated.Team members only: update environment variables in override, staging and production env. files and trigger update config script.API documentation has been updated (if necessary) (see docs on API documentation).