Not really reporting a problem but a change ... with a question below *.
mdeploy has changed ...
In updating a site to current version 3.5.1+ and getting plugin updates as well.
it appears that mdeploy usage of moodledata/mdeploy is no longer.
Rather, mdeploy now using:
archive directory at above location copies of the plugin directories updated
in zips examples ...
-rw-rw-rw- 1 apache apache 5010290 Aug 12 06:54 2018062900.zip
-rw-rw-rw- 1 apache apache 2129147 Aug 12 06:47 2017120400.zip
-rw-rw-rw- 1 apache apache 52803 Aug 12 06:48 2018050900.zip
and in distfiles (the newest downloaded):
[root@site code_manager]# ls -l distfiles
-rw-rw-rw- 1 apache apache 2096098 Aug 12 06:47 1acd94081cdf200b6cc4ae2551bbdeba.zip
-rw-rw-rw- 1 apache apache 5014071 Aug 12 06:49 51d94dc3d1015bc9cf5e19f09f156bc4.zip
-rw-rw-rw- 1 apache apache 54580 Aug 12 06:48 5ffb7eb9ea308ea55c68a7feca277ddc.zip
All this to say, that in the past, it might have been advised to delete the contents of
temp directory for space issues or for other issues - such as theme.
Old advice might not apply any more as I would think one would need to keep
moodledata/temp/core_plugin ... whose name suggest future direction?
Also, minimlal backups of moodledata had been considered filedir ... might now
also include moodledata/temp/core_plugins/
Am assuming the old /moodledata/mdeploy directory is no longer needed and can
be safely removed.
Sure would be nice to have that mdeploy.log back again, however.
One might need to increase php limits for time for a script to run ... observation ... especially large addons/plugins will take time to zip and store in the archive. Was getting concerned that an update to the SAML2 as an example would time out it was taking so long with no progress info available on screen or in logs of any kind that one could watch. The other addon on this site that's 'large' ... Essentials theme.
'spirit of sharing', Ken