-
Notifications
You must be signed in to change notification settings - Fork 10
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
Added stopping of docker containers when ExApp is disabling. Timeout of enable/disable increased to 60. #430
Conversation
…enable/disable increased to 60. Signed-off-by: Alexander Piskun <[email protected]>
/backport to stable30 |
The backport to # Switch to the target branch and update it
git checkout stable30
git pull origin stable30
# Create the new backport branch
git checkout -b backport/430/stable30
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c8b0c59e
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/430/stable30 Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
/backport to stable29 |
The backport to # Switch to the target branch and update it
git checkout stable29
git pull origin stable29
# Create the new backport branch
git checkout -b backport/430/stable29
# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick c8b0c59e
# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/430/stable29 Error: Failed to cherry pick commits: error: no cherry-pick or revert in progress Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
After the previous PR(#430) which added stopping application containers feature when shutting down, as @andrey18106 correctly noted during our 1:1 conversation: we cannot rely on the application inside the docker container to be ready to process the request at the moment the docker container is turned on. This PR introduces handling of it by checking health-check and heartbeat. Signed-off-by: bigcat88 <[email protected]>
Added stopping of docker containers when ExApp is disabling. Timeout of enable/disable increased to 60. Manual backport of #430 Signed-off-by: Alexander Piskun <[email protected]>
If ExApp is resource-heavy, stopping it now does not always free up resources (only if it is implemented in ExApp itself, which is quite rare)
That is why we add this PR to turn off the docker container when clicking the "disable" button on ExApp.
With "manual installation" - nothing changes, we have nothing to turn off and this is not supported.
Also, the timeout for a request to ExApp to turn on/off has been raised from 30 seconds to 60 seconds, which is still acceptable for UI so as not to seem slow;
Resolves: #410