https://bugzilla.wikimedia.org/show_bug.cgi?id=62550
Bryan Davis <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #1 from Bryan Davis <[email protected]> --- This happens because the Exec['update database'] puppet step only happens when the contents of the extension specific settings file change. In the given workflow, the puppet run triggered by the second `vagrant up` command will check settings.d/puppet-managed/10-Flow.php and find that the current file on disk has the correct sha1 and thus not fire the notify event that triggers the database update. It should be possible to use the vagrant plugin API's `action_hook` call as part of the MediaWiki-Vagrant plugin to install a routine to run following `vagrant destroy` that would clean up the various puppet-managed settings files in settings.d. This would mimic the manual `rm` of the extension settings. I have a `dist-clean.sh` script that I use to reset the Vagrant environment that I use for testing pending gerrit commits which does something similar: #!/usr/bin/env bash set -e vagrant destroy -f rm settings.d/puppet-managed/* git checkout -- settings.d/puppet-managed/README rm -rf settings.d/multiwiki/ rm -rf puppet/manifests/manifests.d/vagrant-managed.pp rm -rf .settings.yaml -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
