Closed RealLukeMartin closed 9 years ago
That's true, with the ansible switch coming this is just temporary bloat. Going to try out vagrant reload --provision
when I see this issue again and see how it goes.
I just hit this issue again after doing a vagrant up today. vagrant reload --provision
did not work, but drush @v provision-verify
did. Not going to worry about it now though while the ansible switch is going on, it may be resolved after all that.
Anyway, the root of this is that I've reached the limit of my willingness to keep fighting with Puppet. As a result, we're already well on our way to having the components ready to switch to Ansible. Better yet, they'll all be covered by tests, both individually and in combination.