this is an old bug, but its hugely mitigated in practice. There was a fix applied to process debug hooks/debug logs settings several months ago. Given the time for machine provisioning, its fairly straight forward to debug install/start hooks doing the logical thing.. ie.
The local provider being a bit faster to deploy (a few seconds), does require the debug-hooks command fairly soon after deploy, but that seems fairly minor.
this is an old bug, but its hugely mitigated in practice. There was a fix applied to process debug hooks/debug logs settings several months ago. Given the time for machine provisioning, its fairly straight forward to debug install/start hooks doing the logical thing.. ie.
juju bootstrap
juju deploy wordpress
juju debug-hooks wordpress/0
should work without issue.
The local provider being a bit faster to deploy (a few seconds), does require the debug-hooks command fairly soon after deploy, but that seems fairly minor.