fix: require user confirmation to delete other php version in Debian #92
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.
Description
By auto delete another version from the machine, it causing existing service which depend to the version break and system down. Better if the purge mechanism require to confirm manually from executor (user) instead.
Example Case
We have legacy service running with PHP 7.x fpm, depend to binary /usr/sbin/php-fpm7.2 running under systemd with command below:
When new service with newest PHP binary dependency coming, require devOps to install the binary, by using this roles the previous binary will be removed automatically in the task
Purge PHP version packages (besides the currently chosen php_version).
. Then when the legacy service owner deploy their service, it will break.Powered by dPanel