Enhance "Disable App" Functionality to Fully Stop the App Container #410
Description
Currently, in AppAPI, disabling an app simply involves sending the value 0 to the /enabled endpoint. This action doesn’t fully turn off the application but rather signals that it is disabled. While this signal prevents the app from making other API calls (returning 401 responses for other requests), the app itself remains running.
Proposed Improvement:
In addition to sending 0 to the /enabled endpoint, I suggest we fully stop the entire container after calling /enabled.
This would have the following benefits:
- Applications utilizing GPU resources can correctly release memory(it will be done by host OS).
- It will reduce resource consumption when an app is disabled.
- This change should not break backward compatibility, as we will still send
0to the/enabledendpoint, maintaining the current signaling behavior.
This improvement would be particularly useful given that we currently do not have overly complex ExApps, ensuring a smooth transition without disrupting existing functionality.