Comment 6 for bug 1517588
Revision history for this message
| Devdatta Kulkarni (devdatta-kulkarni) wrote | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
There is also the question of whether or not to delete the DU image corresponding to an app as part of the 'solum app delete' call.
The options we have are, (a) always delete the image corresponding to the app, (b) never delete the image, (c) make the image delete condition upon a command line flag.
There are drawbacks of both option (a) and (b).
If we always delete the image upon app delete, it would not be possible to support the requirement of deploying an app starting from an already built image, which is one of the features that we want to support.
If we never delete the image, the images would grow in proportion to the number of app deploy actions, which can be huge if an app is defined to be deployed via CI/CD based triggers.
Therefore option (c) is the best option.
We can support it as follows:
On Solum command line:
solum app delete --deleteImage <appId>
On the API side, the flag can be implemented as a query parameter to the DELETE call
DELETE /apps/<